#9103 closed bug (fixed)
.attr('foo', true) not setting related DOM property
Reported by: | crescentfresh | Owned by: | |
---|---|---|---|
Priority: | blocker | Milestone: | 1.6.1 |
Component: | attributes | Version: | 1.6 |
Keywords: | Cc: | ||
Blocked by: | Blocking: |
Description
(Note: this is the inverse of #9094)
In light of the 1.6 reversions to .attr()
to match pre-1.6 behavior wrt boolean properties, .attr('foo', true)
is broken. See http://jsfiddle.net/4XmRM/
Change History (3)
comment:1 Changed 12 years ago by
comment:2 Changed 12 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
Set the property corresponding to a boolean attribute when setting to true. Fixes #9103.
- Once boolean properties had been modified natively, setting the attribute no longer set the current value Changeset: 5195335cf4df62c06488807ae857f64c2d549253
comment:3 Changed 12 years ago by
Component: | unfiled → attributes |
---|---|
Milestone: | 1.next → 1.6.1 |
Priority: | undecided → blocker |
Note: See
TracTickets for help on using
tickets.
I'm sorry, report should read "In light of the 1.6.1 reversions..."