Side navigation
#10274 closed bug (duplicate)
Opened September 14, 2011 09:41AM UTC
Closed September 14, 2011 03:47PM UTC
Last modified March 09, 2012 11:17PM UTC
checked broken for radio buttons
Reported by: | sam.garnham@l-3com.com | Owned by: | |
---|---|---|---|
Priority: | low | Milestone: | None |
Component: | attributes | Version: | 1.6.4rc1 |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
Reproduced with both 1.6.3 and 1.6.4 - fine in 1.6.2.
Two radio buttons with second checked. onclick of first, attr("checked") still returns "checked" for the second.
Attachments (0)
Change History (5)
Changed September 14, 2011 01:28PM UTC by comment:1
component: | unfiled → attributes |
---|---|
priority: | undecided → low |
resolution: | → worksforme |
status: | new → closed |
Changed September 14, 2011 03:47PM UTC by comment:2
resolution: | worksforme |
---|---|
status: | closed → reopened |
This is legit. We have the boolHook in place so that attr will work as it did before for booleans. We encourage people to use prop for boolean attributes, but attr should work as well until it is officially deprecated. I'm marking this ticket as a dupe of a later one.
Changed September 14, 2011 03:47PM UTC by comment:3
resolution: | → duplicate |
---|---|
status: | reopened → closed |
Changed September 14, 2011 03:53PM UTC by comment:5
Thanks for the clarification on this one timmywil!
Thanks for submitting a ticket. I've reviewed your test case and I believe you're incorrectly using .attr() rather than .prop() to check for the checked value. If you take a look here, a corrected version of your test case works fine with both jQuery 1.6.2,.3 and edge (.4). http://jsfiddle.net/addyosmani/uvpAc/3/
See here for just one of the explanations behind .attr() vs .prop() (noting that this change was introduced in jQuery 1.6): http://forum.jquery.com/topic/please-explain-attr-vs-prop-change-in-1-6