Skip to main content

Bug Tracker

Side navigation

#12835 closed bug (invalid)

Opened November 02, 2012 11:57AM UTC

Closed December 06, 2012 09:05AM UTC

select - onchange bug

Reported by: Owned by:
Priority: undecided Milestone: None
Component: unfiled Version: 1.8.2
Keywords: Cc:
Blocked by: Blocking:

When assigning an eventhandlerto the onChange event of a SELECT element, it only triggers if the user uses the mouse and clicks another element in the list. If the user has clicked once, but then navigates the list using the arrow buttons (up-/down) on the keyboard, the onChange eventhandler is not triggered.

A workaround for now is assigning both onChange and keyUp event handlers to the SELECT element:



I am not sure whether this is a bug or not, but for me it seems quite obvious that an onChange event is triggered when a new option in the SELECT element is chosen, either by clicking on it with the mouse, or by navigating to it using the up-/down arrow buttons on the keyboard.


Firefox 16.0.2@Mint

Attachments (0)
Change History (2)

Changed November 21, 2012 06:47PM UTC by dmethvin comment:1

owner: →
status: newpending

Thanks for taking the time to contribute to the jQuery project! Please provide a complete reduced test case on jsFiddle to help us assess your ticket. Additionally, be sure to test against the jQuery Edge version to ensure the issue still exists. To get you started, use this boilerplate: Open the link and click to "Fork" (in the top menu) to get started.

Changed December 06, 2012 09:05AM UTC by trac-o-bot comment:2

resolution: → invalid
status: pendingclosed

Because we get so many tickets, we often need to return them to the initial reporter for more information. If that person does not reply within 14 days, the ticket will automatically be closed, and that has happened in this case. If you still are interested in pursuing this issue, feel free to add a comment with the requested information and we will be happy to reopen the ticket if it is still valid. Thanks!