Open
Bug 423719
Opened 17 years ago
Updated 3 years ago
Incorrect mouseOut triggered when using select element
Categories
(Core :: General, defect)
Core
General
Tracking
()
NEW
People
(Reporter: offsky, Unassigned)
References
(Blocks 1 open bug, )
Details
When using FFb4 on Mac 10.5.2, an incorrect mouseOut event is triggered when selecting an option from a select element.
The options for a select element seem to appear with a 1 pixel gap between the control and the menu, which means that when you move your mouse down to select one of the options, you get a mouseOut event triggered before you reach any of the options. This event was not fired in FFb3, and is not fired in other web browsers.
Please see the reduced testcase URL attached to this bug.
This may be another bug, but I am also getting mouseOut events fired each time the mouse moves over a different option. The mouseOut event is attached to the select element, not the options, so I dont think all these events should be firing, and they don't fire in Safari and Opera (didnt test IE).
Comment 1•17 years ago
|
||
I see the 1-pixel gap on OS X and Linux, but not on Windows. And I
see "moved from selectelement to htmltag" (as I slowly move the mouse
down from the select element towards the options) on OS X and Linux,
but not on Windows.
But I believe custom (i.e. non-native) comboboxes are used on all
three platforms. Is even the behavior on Windows entirely correct?
Comment 2•17 years ago
|
||
On general principles I'm changing hardware and OS to "all" ... so non-Mac folks will be more likely to notice this :-)
OS: Mac OS X → All
Hardware: Macintosh → All
Comment 3•17 years ago
|
||
bug 297080 fixed spurious mouse out events which was integrated after beta 4. Maybe this improved things here?
Updated•17 years ago
|
Component: OS Integration → General
Product: Firefox → Core
QA Contact: os.integration → general
Reporter | ||
Comment 4•17 years ago
|
||
Just tested with beta 5 and the bug still exists.
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•