Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 312013

Summary:	[Help] Help window is disabled when Import dialog is opened
Product:	[Eclipse Project] Platform	Reporter:	Michal Nowak <mnowak>
Component:	User Assistance	Assignee:	platform-ua-inbox <platform-ua-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	minor
Priority:	P3	CC:	cgold, chandrayya.gk, overholt
Version:	4.0
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:	stalebug

Description Michal Nowak

2010-05-07 04:00:17 EDT

Build Identifier: Build id: M20100211-1343

I noticed that I can't use Help (Help->Help Contents) when e.g. "Import" (as
Import Project) window is opened. I guess just the main Eclipse window from
which Help was opened should be disabled but not the Help window itself.

eclipse-platform-3.5.2-3.2.el6.i686

Actual results:

You can't scroll/interact Help until Import is finished.

Expected results:

Help window accessible all the time.

Additional info:

(Could be caused by move from jetty -> jetty-eclipse? I guess not.)

Downstream bug: https://bugzilla.redhat.com/show_bug.cgi?id=589241

Reproducible: Always

Steps to Reproduce:
1. Create project
2. Open Help
3. File -> Import...

Comment 1 Andrew Overholt

2010-05-07 07:27:47 EDT

Michal's comments about the RPM version and the jetty dependency can be ignored.  He's only concerned with the modality of the windows.

Comment 2 Chris Goldthorpe

2010-05-26 14:17:54 EDT

I was able to reproduce this on Linux. Eclipse on Windows does not have this problem because it launches the browser on a separate thread, I'm not sure why Linux does not also use a separate thread for the browser. I will investigate more.

Comment 3 Chandrayya

2013-12-18 05:17:35 EST

Its not only with import wizard. If any wizards or dialogs are kept opened then help window will not respond till we closes all these wizards and dialogs.

Comment 4 Eclipse Genie

2019-09-24 13:17:14 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.

If you have further information on the current state of the bug, please add it. 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.