#3786 closed bug (fixed)
removeAttr should use jQuery.props
Reported by: | scottgonzalez | Owned by: | aflesler |
---|---|---|---|
Priority: | high | Milestone: | 1.6 |
Component: | attributes | Version: | 1.5.2 |
Keywords: | attrhooks | Cc: | |
Blocked by: | Blocking: | #8457 |
Description
removeAttr sets the value to empty string using attr, which uses jQuery.props, but it also calls removeAttribute on the node, which doesn't use jQuery.props.
Change History (6)
comment:1 Changed 14 years ago by
Owner: | set to aflesler |
---|
comment:2 Changed 13 years ago by
Component: | core → attributes |
---|
comment:3 Changed 12 years ago by
Keywords: | attr removeAttr added |
---|---|
Milestone: | 1.3 → 1.4.5 |
Priority: | major → high |
Status: | new → assigned |
Reassigning back to where it was before.
comment:4 Changed 12 years ago by
Keywords: | attrhooks added; attr removeAttr removed |
---|
Note that this may affect the attrhooks rewrite.
comment:5 Changed 12 years ago by
Blocking: | 8457 added |
---|
comment:6 Changed 12 years ago by
Milestone: | 1.next → 1.6 |
---|---|
Resolution: | → fixed |
Status: | assigned → closed |
Version: | 1.2.6 → 1.5.2 |
Note: See
TracTickets for help on using
tickets.
Still applies in 1.4.3. Looking at jQuery.props I am not sure that all of them should be applied to removeAttribute. Definitely requires some testing.