#11667 closed bug (duplicate)
[checked] selector failure
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | undecided | Milestone: | None |
Component: | unfiled | Version: | 1.7.2 |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
Using a selector that contains [checked] as well as another [attr] selector fails, while using :checked or applying .filter('[checked]') separately to the same selector works as expected. See a detailed example here: http://jsfiddle.net/bgmort/V3KqD/
Change History (3)
comment:1 Changed 11 years ago by
comment:2 Changed 11 years ago by
Resolution: | → duplicate |
---|---|
Status: | new → closed |
Found the duplicate ticket, which also points out we can't fix this until we remove the boolHook that fixes old broken uses of .attr()
. BTW, thank you for the extensive test case!
Note: See
TracTickets for help on using
tickets.
Interesting. Some relevant spec: There is a failure, but I think you have it backwards.
So,
"[checked]"
should only apply to elements that had achecked
attribute initially set in their HTML. The.filter("[checked]")
would be wrong then, I suspect it is going through Sizzle and looking at the property rather than the attribute. If so there's already a ticket for that and I'll look at it later.