Side navigation
#9495 closed bug (invalid)
Opened June 02, 2011 03:03PM UTC
Closed June 24, 2011 07:57AM UTC
$(...).change() on radio not working when using keyboard to change selection in WebKit browsers
Reported by: | matthias@unusuals.net | Owned by: | matthias@unusuals.net |
---|---|---|---|
Priority: | low | Milestone: | 1.next |
Component: | event | Version: | 1.6.1 |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
In WebKit based browsers like Chrome and Safari, the change event isn't fired when using the keyboard to change the selection. Using the mouse works like expected.
Short sample code:
<input type="radio" name="tester" value="1" /> <input type="radio" name="tester" value="2" /> <script type="text/javascript">$('input').change(function() { console.log("fired"); });</script>
Attachments (0)
Change History (5)
Changed June 02, 2011 03:54PM UTC by comment:1
component: | unfiled → event |
---|---|
priority: | undecided → low |
Changed June 02, 2011 04:02PM UTC by comment:2
Using Safari Version 5.0.5 (6533.21.1) on Mac OS X 10.6.7 Build 10J869.
This fiddle works for me when I hit space after selecting the first empty radio button. It doesn't work when hitting the right or left arrow keys.
What I did:
- Open the link
- Clicked on "Result" part on white background
- Hit tab: first radio button becomes selected.
- Hit space: "fired" gets printed in the console
- Hit right arrow key: second radio button becomes selected, no "fired" in the console.
A workaround is mentioned here: http://evilstreak.co.uk/blog/fixing-change-events-on-radios
Changed June 04, 2011 05:33PM UTC by comment:3
owner: | → matthias@unusuals.net |
---|---|
status: | new → pending |
Has this been reported as a bug to the Safari/Chrome teams? Seems like they should be able to fix it.
We might be able to do it via a special event handler but then we'd also need to figure out a feature detect to determine whether/when it is needed and based on your description I am not sure that is possible.
Changed June 09, 2011 09:48AM UTC by comment:4
Don't no, I havn't reported it because I didn't know which product is affected.
Changed June 24, 2011 07:57AM UTC by comment:5
resolution: | → invalid |
---|---|
status: | pending → closed |
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!
This works for me in both Chrome and Safari
http://jsfiddle.net/timmywil/wZyRJ/