Ticket #9191 (closed bug: fixed)
attr checked difference
| Reported by: | arnaud@… | Owned by: | arnaud@… |
|---|---|---|---|
| Priority: | low | Milestone: | 1.6.1 |
| Component: | attributes | Version: | 1.6 |
| Keywords: | Cc: | ||
| Blocking: | Blocked by: |
Description
the bug affect jquery 1.6 (no bug on jquery 1.5) :
HTML : <form> <input class="class1" type="radio" name="l1" value="0" checked="checked" /> <input class="class2" type="radio" name="l1" value="1" /><br /> <input class="class1" type="radio" name="l2" value="0" checked="checked" /> <input class="class2" type="radio" name="l2" value="1" /> </form>
JS :
$('.class2').attr('checked','checked'); this works on FF4 but not in I9 $('.class1').attr('checked','checked'); does not work
Change History
comment:1 Changed 2 years ago by timmywil
- Owner set to arnaud@…
- Priority changed from undecided to low
- Status changed from new to pending
- Component changed from unfiled to attributes
comment:2 Changed 2 years ago by anonymous
try it here : http://jsfiddle.net/6PxNR/ work with jquery 1.5.2 but bug with jquery 1.6
comment:3 Changed 2 years ago by timmywil
- Status changed from pending to closed
- Resolution set to fixed
- Milestone changed from 1.next to 1.6.1
This has been changed for 1.6.1, but I recommend using prop for dynamically changing the checked property. The checked attribute is technically only meant to store the default or initial value, which is why 1.6 behaves the way it does. We understand this caused confusion which is why jQuery in 1.6.1 will behave as it did previously, but prop is still recommended if for no other reason than it will be faster.
comment:7 Changed 2 years ago by timmywil
- Summary changed from attr checked bug on radio to attr checked bug
Please follow the bug reporting guidlines and use jsFiddle when providing test cases and demonstrations instead of pasting the code in the ticket.

Thanks for taking the time to contribute to the jQuery project! Please provide a reduced test case on http://jsfiddle.net that reproduces the issue experienced to help us assess your ticket.
Additionally, test against the jQuery (edge) version to ensure the issue still exists.