#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 8 years ago by dmethvin
- Owner set to aflesler
comment:2 Changed 6 years ago by dmethvin
- Component changed from core to attributes
comment:3 Changed 6 years ago by SlexAxton
- Keywords attr removeAttr added
- Milestone changed from 1.3 to 1.4.5
- Priority changed from major to high
- Status changed from new to assigned
Reassigning back to where it was before.
comment:4 Changed 6 years ago by dmethvin
- Keywords attrhooks added; attr removeAttr removed
Note that this may affect the attrhooks rewrite.
comment:5 Changed 6 years ago by john
- Blocking 8457 added
comment:6 Changed 5 years ago by timmywil
- Milestone changed from 1.next to 1.6
- Resolution set to fixed
- Status changed from assigned to closed
- Version changed from 1.2.6 to 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.