Bug Tracker

Opened 12 years ago

Closed 12 years ago

#8977 closed bug (invalid)

:checked attribute returning the first value, even after changes

Reported by: <[email protected]…> Owned by: <[email protected]…>
Priority: low Milestone: 1.next
Component: attributes Version: 1.6b1
Keywords: Cc:
Blocked by: Blocking:


<input type="checkbox" checked="checked" id="sure"/>
<input type="checkbox" id="unsure"/>

$("#unsure").trigger('change') // checked undefined
$("#unsure").trigger('change') // checked undefined

$("#unsure").trigger('change') // true true
$("#unsure").trigger('change') // true false

Change History (2)

comment:1 Changed 12 years ago by Rick Waldron

Component: unfiledattributes
Owner: set to <[email protected]…>
Status: newpending

Thanks for taking the time to contribute to the jQuery project! Please provide a reduced jsFiddle test case to help us assess your ticket!

Additionally, be sure to test against the jQuery Edge version to ensure the issue still exists.

comment:2 Changed 12 years ago by Timmy Willison

Priority: undecidedlow
Resolution: invalid
Status: pendingclosed

That is the correct behavior. This is something that was fixed in attr in 1.6 (removing the ambiguity). .attr('checked') retrieves the actual attribute (which correctly returns undefined as it does not exist on unsure) rather than the property. For DOM properties, use the .prop method. However, the preferred way to check if a box is checked, is with .is(':checked').

Note: See TracTickets for help on using tickets.