Skip to main content

Bug Tracker

Side navigation

#3786 closed bug (fixed)

Opened January 05, 2009 07:57PM UTC

Closed April 10, 2011 08:11PM UTC

Last modified March 09, 2012 09:17AM UTC

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:

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.

Attachments (0)
Change History (6)

Changed January 07, 2009 02:40AM UTC by dmethvin comment:1

owner: → aflesler

Changed June 20, 2010 07:29PM UTC by dmethvin comment:2

component: coreattributes

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.

Changed November 03, 2010 03:35AM UTC by SlexAxton comment:3

keywords: → attr removeAttr
priority: majorhigh
status: newassigned

Reassigning back to where it was before.

Changed November 21, 2010 08:03PM UTC by dmethvin comment:4

keywords: attr removeAttrattrhooks

Note that this may affect the attrhooks rewrite.

Changed March 07, 2011 03:54AM UTC by john comment:5

blocking: → 8457

Changed April 10, 2011 08:11PM UTC by timmywil comment:6

milestone: 1.next1.6
resolution: → fixed
status: assignedclosed