Getting the value of the "value" attribute using .attr("value") is the same as using .val()

[Quozzo]

Using .attr("value") returns the same as using .val() although the "value" attribute remains unchanged in the DOM, as seen by Dragonfly on Opera. New text entered in an input should be returned with .val() but not .attr("value") which should return the value of the "value" attribute, that getAttribute() does.

$('#foo').val() == $('#foo').attr('value')

​http://209.85.12.237/30095/43/0/f5198393/attrbug.htm

[timmywil]

I agree completely. Unfortunately, attr retrieved the value property in the past so we've kept that for backwards compatibility reasons by adding an attrHook for value. I'd like to deprecate that since we have both .val and .prop now. On that note, I'm adding needsreview.

+1 to deprecate in 1.7, remove in 1.8

[addyosmani]

+1

[timmywil]

+1

[gnarf]

In the meantime - If you need attr("value") to be true to the HTML attribute, you can delete $.attrHooks.value- ​http://jsfiddle.net/KxVPH/

[gnarf]

+1

[timmywil]

#10383 is a duplicate of this ticket.

[timmywil]

#10096 is a duplicate of this ticket.

[timmywil]

This also affects Sizzle selections using the value attribute.

[timmywil]

#10731 is a duplicate of this ticket.

[timmywil]

#10823 is a duplicate of this ticket.

[mikesherov]

+1, Tentative +1, although this might get a similar reaction to the .prop stuff introduced in 1.6. However, I think that risk is low, and we can't always be held back by past decisions that are not a good idea in hindsight. Of course, shout from the rooftops about this when the change is made.

[jaubourg]

+0, We need to make sure this doesn't break the web, so to speak.

[jzaefferer]

+0, this needs an actual deprecation first, there's no mention on ​http://api.jquery.com/attr/

[markel]

Maybe its not my place to say this. But please, please dont do this --

1) Its breaking change, a lot of code will not work with this -- ​http://www.google.com/codesearch#search/&q=%5C.attr%5C(%22value%22%5C)%20lang:%5Ejavascript$&type=cs Its not what you promise us --​http://ejohn.org/blog/jquery-16-and-attr/

2) It will be inconsistent with another getters of properties, for example like "checked" and "selected". When user can change input state, not from code, but just clicking on it. Attr will still return a property whereas in html they will stay the same, but for value it will be diffrent?

Distinguish properties and attributes is tempting and logical, but you already make this decision way back. On my opinion -- you have to stick with it.

[Rick Waldron]

+0, It seems obvious right? My concern is BC breakage

[dmethvin]

-1, Needs deprecation first

[timmywil]

@dmethvin: it has already been deprecated. ​http://blog.jquery.com/2011/11/08/building-a-slimmer-jquery/

[timmywil]

#11345 is a duplicate of this ticket.

[dmethvin]

Duplicate of #11735.