Side navigation
#7443 closed feature (invalid)
Opened November 08, 2010 09:40PM UTC
Closed February 18, 2011 07:54AM UTC
Last modified May 20, 2011 07:14PM UTC
Make .text()/.val() interchangable
| Reported by: | john | Owned by: | john |
|---|---|---|---|
| Priority: | low | Milestone: | 1.next |
| Component: | attributes | Version: | 1.5 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
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.
Attachments (0)
Change History (9)
Changed November 08, 2010 09:41PM UTC by comment:1
| component: | unfiled → attributes |
|---|---|
| owner: | → john |
| status: | new → assigned |
Changed November 08, 2010 09:41PM UTC by comment:2
| description: | 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. \ \ jQuery("#test1").text( "Hello" ); → 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/ |
|---|
Changed November 08, 2010 10:15PM UTC by comment:3
| keywords: | → needsdocs |
|---|---|
| priority: | undecided → low |
Changed November 09, 2010 01:55PM UTC by comment:5
| _comment0: | 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. → 1289310945158279 |
|---|
Also, consider the XML/XHTML case in the code; this magic is only intended for HTML DOM documents that have a documented
valueproperty, right? And there's #6478 that will break the proposed
.text()method.
Changed February 03, 2011 10:00PM UTC by comment:6
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
Changed February 04, 2011 01:12AM UTC by comment:7
| milestone: | → 1.next |
|---|---|
| status: | assigned → pending |
| version: | 1.4.3 → 1.5 |
I also think there is no real need to do this, do we still want to do this? John?
Changed February 18, 2011 07:54AM UTC by comment:8
| resolution: | → invalid |
|---|---|
| status: | pending → closed |
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!
Changed May 20, 2011 07:14PM UTC by comment:9
| keywords: | needsdocs |
|---|