Closed
Bug 366365
Opened 18 years ago
Closed 18 years ago
Setting focus to windows is broken in several places
Categories
(SeaMonkey :: UI Design, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 361272
People
(Reporter: Manuel.Spam, Assigned: jag+mozilla)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de-AT; rv:1.8.0.9) Gecko/20061222 SeaMonkey/1.0.7 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a1) Gecko/20070107 SeaMonkey/1.5a It seems like setting a focus to a window is broken at several places. This could be a bug, caused by something in the core, which causes a "focus()" on an item *inside* an window to raise the window to top. An Example for a case, where the window has to get a focus, by focusing an item inside the window could be: http://lxr.mozilla.org/seamonkey/source/suite/common/tasksOverlay.js#87 This and many other functions seem to fail. Even "seamonkey -remote "openURL()"" not longer raises the last active window to top. Reproducible: Always Steps to Reproduce: 1. Get/Compile a SeaMonkey 1.8 build 2. Open Mail/News and Browser 3. Activate the Navigator window 4. Go over "Window" -> "Mail & Newsgroups" in the menu bar of the Navigator. Actual Results: Nothing happens. The Mail/News window doesn't get the focus. Expected Results: - The Mail/News windows should have gotten the focus. - seamonkey -remote openURL should also focus the last active window. It may be possible, that this problem only exists on linux systems.
Comment 1•18 years ago
|
||
This may well be related to bug 330006 and thus bug 295447. The problem for Ctrl+4 is that the chrome window can't take focus (it has no focusable elements) so calling aWindow.focus() actually loses focus. Similarly Ctrl+1 doesn't want call aWindow.focus() either, because that will always focus the URLbar. And the window menu doesn't want to call aWindow.focus() because that won't work properly for any window with an iframe or content area.
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•