<select> sends incorrect value when pressed, moused over, not selected, and then left open




8 years ago
7 years ago


(Reporter: Jason, Unassigned)


Firefox Tracking Flags

(Not tracked)


(Whiteboard: [CLOSEME 2011-1-30])



8 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv: Gecko/20100401 Firefox/3.6.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv: Gecko/20100401 Firefox/3.6.3

Let's say you have a <select> with 4 options. The first option is selected by default. If you click on the dropdown to bring up all the options, mouseover one of the options, and then move your mouse away, the highlighted option is the value that gets returned! I found this through Javascript while doing some mouseover effects based on the value in a <select>.

Reproducible: Always

Steps to Reproduce:
(See http://www.jsfiddle.net/WccFF/ for a working setup)
1. Create a select with a few options (be sure to give them values)
2. Create a div or some other element you can mouse over.
3. Using Javascript, add an event listener to the div that logs the value of the dropdown to the console.
4. Open (click on) the dropdown
5. Mouseover any non-selected option so that it is highlighted
6. Without clicking, move your mouse over the div with the event listener attached
7. View incorrect result
Actual Results:  
The value of the highlighted and abandoned option is returned

Expected Results:  
The value of the actual selected value should be returned
Reporter, are you still seeing this issue with Firefox 3.6.13 or later in safe mode? If not, please close. These links can help you in your testing.

You can also try to reproduce in Firefox 4 Beta 8 or later, there are many improvements in the new version, http://www.mozilla.com/en-US/firefox/all-beta.html
Whiteboard: [CLOSEME 2011-1-30]
No reply, INCOMPLETE. Please retest with Firefox 3.6.13 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Last Resolved: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.