Skip to main content

Bug Tracker

Side navigation

#8889 closed bug (invalid)

Opened April 16, 2011 03:07AM UTC

Closed April 17, 2011 05:46AM UTC

Last modified May 10, 2011 08:44PM UTC

Checkbox showing as checked in DOM but not on Screen

Reported by: anonymous Owned by: anonymous
Priority: low Milestone:
Component: attributes Version: 1.6b1
Keywords: Cc:
Blocked by: Blocking:


This works in jQuery 1.5.2, but it fails in 1.6b1.

Attachments (0)
Change History (6)

Changed April 16, 2011 05:40AM UTC by addyosmani comment:1

owner: → anonymous
status: newpending

Thanks for taking the time to contribute to the jQuery project! Please provide a reduced test case on that reproduces the issue experienced to help us assess your ticket!

Additionally, test against the jQuery (edge) version to ensure the issue still exists.

Changed April 16, 2011 11:20PM UTC by anonymous comment:2

status: pendingnew

I (i.e. someone else) also have the problem.

I created a jsFiddle here (click the checkbox a few times):

It worked before, not in 6b1.

I do not know how to test with the "jQuery (edge)" version. Perhaps this should be explained somewhere in the "how to file a bug" section :)

Changed April 17, 2011 05:46AM UTC by timmywil comment:3

component: unfiledattributes
priority: undecidedlow
resolution: → invalid
status: newclosed

The checked attribute doesn't actually change and is not actually present in your fiddle. You are thinking of the property. You can use .prop("checked") or .is(":checked") to see if a checkbox is checked. The latter is preferable.

Changed April 17, 2011 06:36PM UTC by qwertymk comment:4 should be what you want

Changed April 19, 2011 04:25PM UTC by anonymous comment:5

Interesting, thank you. Stupid mistake on my part. But I had been using it since a year ago, across my entire application, most likely because I had read somewhere that I could do it like that. And that was in fact correct, at least until jQuery 1.5.2.

So I'm just making this last comment to prepare y'all for a bunch of people that may have partly broken applications as soon as 1.6 is released, if they automatically adopt it :) I realise that this is 'their fault', because they, like me, used a 'wrong' approach, but to them it may feel like something that's not backwards compatible. It's something that (erroneously) worked, but no longer does.

Changed May 10, 2011 08:44PM UTC by JorisDebonnet comment:6

Ha! I'm a prophet. (see above comment, and 1.6.1rc notes)

(.. I should however have registered before actually writing that comment)