Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 346141 - Help window should not freeze when a dialog window has grabbed the focus
Summary: Help window should not freeze when a dialog window has grabbed the focus
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: User Assistance (show other bugs)
Version: 3.6.2   Edit
Hardware: Other Linux-GTK
: P3 normal with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: platform-ua-inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-17 14:52 EDT by Corey Ashford CLA
Modified: 2020-07-28 13:14 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Corey Ashford CLA 2011-05-17 14:52:48 EDT
Build Identifier: M20110210-1200

If I bring up a help window, and then start a project creation wizard, for example, the help window no longer responds to any user action.

This is *very* inconvenient, if you are new to Eclipse, or new to a particular plug-in and you are trying to use the Help page to step you through dialog settings.


Reproducible: Always

Steps to Reproduce:
1.Start up Eclipse, and select Help->Help Contents, and wait for the Help window to come up
2. In Eclipse, select File->New->Project...
3. Set your focus back to the Help window and try to use it.  You will see that it doesn't respond to any user input.  In fact, you can't even close the Help window.
Comment 1 Chris Goldthorpe CLA 2011-08-24 12:39:43 EDT
What platform are you running on? I think this is an issue with the way that SWT works on Linux and I agree that it is very annoying.
Comment 2 Corey Ashford CLA 2011-08-24 14:43:59 EDT
We are using Linux GTK.  So yeah, I didn't realize that it worked better on Windows (etc.)

I have changed the Platform to "Other -> Linux - GTK"
Comment 3 Eclipse Genie CLA 2020-07-28 13:14:51 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.