Community
Participate
Working Groups
Steps to reproduce: 1. Open a wizard with at least two pages and help button visible (the one in lower left corner). Example: open Source -> Externalize String... 2. Click Next (do not click anywhere else on wizard) 3. Click Help button (do not click anywhere else on wizard before this) Result: The context help does not open. Workaround: Click anywhere else on the wizard and then click the help button. The context help opens properly. I was able to reproduce it on Eclipse Neon as well as Oxygen 1a. Apologies if am filing it against the wrong component.
(In reply to Ankur Sharma from comment #0) > Steps to reproduce: > > 1. Open a wizard with at least two pages and help button visible (the one in > lower left corner). Example: open Source -> Externalize String... > > 2. Click Next (do not click anywhere else on wizard) > > 3. Click Help button (do not click anywhere else on wizard before this) > > Result: > The context help does not open. > > Workaround: > Click anywhere else on the wizard and then click the help button. The > context help opens properly. > > I was able to reproduce it on Eclipse Neon as well as Oxygen 1a. > > > Apologies if am filing it against the wrong component. Over to JDT UI for investigation.
I can reproduce it with the latest Photon I-build using "Source -> Externalize String..." wizard. But I could not reproduce it with any other wizard having two or more pages. Ankur, do you have any other example as well where you see this issue?
Created attachment 271439 [details] Sample Wizard to reproduce the problem My bad. I forgot to mention that the use case is not about Externalize String wizard but for the RCP contributed wizard. Please find a sample plugin which contributes a wizard to reproduce the problem. Hope that helps
I am not able to reproduce the issue with the attached sample wizard. However, "Source -> Externalize String..." wizard should help in debugging the problem.
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.
