Since 1.7 (and probably from bug 284664), we've started firing mouseout on an element that was removed from the document while the mouse was over it *after* the element is removed from the document. Firing mouseout on the element when it is no longer in the document seems wrong. I think we should either: 1. (preferable, I think, since it's compatible with 1.7 and IE/Windows) not fire the mouseout at all, or 2. fire the mouseout before the element is removed from the document. This has been causing me some problems with my patch on bug 241518. Roc, any thoughts? Was this change intentional? Steps to reproduce: 1. load attachment 182012 [details] 2. move the mouse slowly over the yellow box Expected results: After one second, an alert showing: mouseover starting remove ending remove Actual results: After one second, an alert showing: mouseover starting remove ending remove mouseout
Comment on attachment 182017 [details] [diff] [review] patch it was not intentional. Just a byproduct of making mouseover use content instead of frames (which is still the right thing!)
Attachment #182017 - Flags: approval1.8b2?
Status: NEW → ASSIGNED
Priority: -- → P2
Target Milestone: --- → mozilla1.8beta2
Comment on attachment 182017 [details] [diff] [review] patch a=asa
Attachment #182017 - Flags: approval1.8b2? → approval1.8b2+
Fix checked in to trunk, 2005-04-28 13:47 -0700.
Status: ASSIGNED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.