Community
Participate
Working Groups
Created attachment 287752 [details] adjusted screen shot Version: 2021-09 (4.21) Build id: I20210906-0500 When starting a JUnit plugin test that triggers the cannot-set-breakpoint dialog, the dialog may be occluded as suggested by the attached screen shot. The dialog should be in front of the nested Eclipse window. The attached screen shot has been adjusted to move the nested Eclipse window to one side so that the underneath popup is shown for this report. In its natural form, the dialog is fully occluded and the underlying debugger shows everything "running", which is not true. Everything is "suspended" awaiting the completion of the launch activites. On a single screen, an impatient user can discover the cause of nothing happening by clicking on the underlying debugger revealing the hidden dialog. On a multiple screen with the debugger on the second screen, the popup can be more obscurely occluded. Since the popup is modal, the user can be well-confused by the failure of an all-running debugger to respond to e.g. stop.
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.
Cannot be stale until triaged by a relevant comnmitter.
