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

Bug 335968

Summary: Wrong shell active after Alt+Tab with modeless child shell on Windows 7
Product: [Eclipse Project] Platform Reporter: Markus Keller <markus.kell.r>
Component: SWTAssignee: Platform-SWT-Inbox <platform-swt-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3 CC: Silenio_Quarti
Version: 3.7Keywords: accessibility
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard: stalebug

Description Markus Keller CLA 2011-02-01 09:57:48 EST
I20110127-2034, Windows 7 (is OK on Windows XP)

- ControlExample > Shell
- click SWT.SHELL_TRIM and Parent
- click Create Shell
- Alt+Tab to another window
- Alt+Tab

=> was: ControlExample shell active
=> expected: child shell should be active

This is also a problem in the SDK, e.g. when you are in a text editor and open the Find/Replace dialog (Ctrl+F).
Comment 1 Markus Keller CLA 2011-03-23 13:19:59 EDT
This is quite annoying, since it affects all modeless shells.
In the SDK, this also includes detached views.
Comment 2 Markus Keller CLA 2011-04-21 09:17:41 EDT
I can also reproduce a similar problem with the refactoring preview window (e.g. inline method > "Preview >").

However, that dialog is SWT.DIALOG_TRIM | SWT.APPLICATION_MODAL | SWT.MAX | SWT.RESIZE, but I cannot reproduce the same problem in the ControlExample.
Comment 3 Markus Keller CLA 2012-01-22 16:46:55 EST
This doesn't happen when I switch applications using the task bar, but it also happens on Windows+Tab.

With the Find/Replace dialog, this bug is just annoying, but there are other cases, where I don't know how to bring focus into the dialog again without clicking it (e.g. Pull and Fetch Result dialogs in EGit nightly, see bug 35886).
Comment 4 Lars Vogel CLA 2019-11-14 03:09:30 EST
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.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.