User-Agent: Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040116 Sometimes -- but not always -- moving the mouse over a flash plugin in a Mozilla window will cause that window to auto-raise (move to the top of the window stack.) Application windows should never, ever auto-raise themselves -- that's a decision that must be left to the window manager. Reproducible: Always Steps to Reproduce: I don't fully understand the conditions under which the window auto-raises, but I can reproduce it at will. 1. Open http://www.macromedia.com/software/flash/ in a Mozilla window on the left side of the screen. 2. Place any other window to the right, such that it overlaps the Mozilla window by about half. 3. Raise the window on the right, and leave the mouse inside it. 4. Move the mouse from the right window to the left window such that when the mouse enters the left window, it is on top of the Flash rectangle (the menu-bar thingy at the top of the page.) 5. The left window should have auto-raised. 6. If it did not, slowly move the mouse upward, toward the menubar. It should raise when the mouse leaves the Flash rectangle and enters the URL bar / toolbar. The weird thing about this is, if the transition from the R to L window occurs over a part of the document that is *not* Flash, the auto-raise thing doesn't happen. It seems to only happen if you move directly from one window to the flash portion of another window. It sounds like someone is probably confused about the "detail" member of XCrossingEvent, since the behavior seems to depend on which variety of EnterNotify/LeaveNotify event was generated. Mozilla 1.6 - Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040116 Red Hat Linux release 9 (Shrike) Linux.jwz.org 2.4.20-8smp #1 SMP Thu Mar 13 16:43:01 EST 2003 i686 athlon i386 Gnome 1.4 (gnome-libs-1.4.2-0.ximian.6.8) Window manager: sawfish-1.3-1 in point-to-type (focus follows mouse) mode
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: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
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.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.