Make .text()/.val() interchangable

[john]

Right now there is a lot of confusion over when to use .text() or .val(). We could simplify it by making it such that .text() will set the value of input elements and textareas. No reason not to.

 http://jsfiddle.net/wt9tu/

[dmethvin]

See also #6827.

[dmethvin]

Also, consider the XML/XHTML case in the code; this magic is only intended for HTML DOM documents that have a documented value property, right? And there's #6478 that will break the proposed .text() method.

[etiger13]

A reason not to would be that it promotes using .text() to set the value of an input. Users could start thinking that it sets the value for everything, including <option>s, which is not the case. .text sets the text of an element and .val sets the value. Simple to understand. Just because we can promote bad coding standards doesnt mean its the right thing to do

[jitter]

I also think there is no real need to do this, do we still want to do this? John?

[trac-o-bot]

Because we get so many tickets, we often need to return them to the initial reporter for more information. If that person does not reply within 14 days, the ticket will automatically be closed, and that has happened in this case. If you still are interested in pursuing this issue, feel free to add a comment with the requested information and we will be happy to reopen the ticket if it is still valid. Thanks!