Skip to main content

Bug Tracker

Side navigation

#6634 closed bug (duplicate)

Opened June 04, 2010 10:52AM UTC

Closed June 16, 2010 02:35AM UTC

form attributes somtimes become readonly and then .attr() doesn't work anymore

Reported by: AL13N Owned by:
Priority: Milestone: 1.4.3
Component: attributes Version: 1.4.2
Keywords: Cc:
Blocked by: Blocking:

i thought i found a bug in FF:

but if you read the response i got from the mozilla team, you see that it's a "feature".

how does it work exactly?

if you have a form, and you have a form element in it, with name or id having one of the attribute names of that form (name, action, ...), the form attribute in question becomes readonly with the generic accessors (the property), however, the setAttribute() function works as a workaround.

in my code i had to do:

.attr(k, v)

IF .attr(k) != v

.get(0).setAttribute(k, v)

my proposal is to fix this workaround inside the .attr() function. so that this "feature", will not be problematic with all those users. it lost huge amounts of time due to this "feature"

Attachments (0)
Change History (1)

Changed June 16, 2010 02:35AM UTC by dmethvin comment:1

resolution: → duplicate
status: newclosed

Duplicate of #3113.