Problems with focus when using X-Mouse (focus follows mouse)




Event Handling
16 years ago
13 years ago


(Reporter: eric lindvall, Unassigned)


Windows XP

Firefox Tracking Flags

(Not tracked)




16 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2b) Gecko/20021021 Phoenix/0.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2b) Gecko/20021021 Phoenix/0.3

When using the Tweak UI (for Windows XP - feature
"X-Mouse" or "Activation follows mouse" (focus follows mouse, in X), windows
don't always stay in the order they should be durring some operations.

Reproducible: Always

Steps to Reproduce:
1. Open the "Preferences" window
2. make sure the window is on top of a browser window
2. go to Advanced -> Images
3. click on "Manage Images..."
4. click "Close"

Actual Results:  
the browser window pops in front of the Preferences window

Expected Results:  
the preferences window should still be on top.

It seems if the preferences window and the Manage Images windows are not in
front of a browser window, everything behaves how it should.

Comment 1

16 years ago
related to or a dupe of bug 144025 or bug 80997 ?

Comment 2

16 years ago
it doesn't look like this is actually a duplicate of either.

i did not mention it, but i do not have "autoraise when activiting" enabled.

maybe i'm wrong, but bug 144025 sounded like a DHTML issue, and bug 80997 seems
to be related to autoraise and focus stealing, instead of window ordering.

Comment 3

16 years ago
eric, did you test the latest build of Mozilla? If this is a general problem
with our application focus that impacts Mozilla as well then the bug is misfiled
and should be moved to the Mozilla product. 

Comment 4

16 years ago
i just got mozilla 1.2 and installed it, and it has the same problem.

Comment 5

16 years ago
Reassigning this to Mozilla->Event Handling.
Component: General → Event Handling
Product: Phoenix → Browser
Version: unspecified → other

Comment 6

15 years ago
->default contacts
Assignee: blake → events
QA Contact: asa → ian
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.