Side navigation
#4046 closed bug (worksforme)
Opened February 02, 2009 09:34PM UTC
Closed August 09, 2009 12:58AM UTC
.attr("value") 1.2.6 versus 1.3.1
| Reported by: | bdenosky | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | 1.3.2 |
| Component: | unfiled | Version: | 1.3.1 |
| Keywords: | Cc: | ||
| Blocked by: | Blocking: |
Description
xhtml snippet: <p id="bpUsername"><input name="bpUsername" type="text"/></p>
jquery snippet: alert($("#bpUsername input").attr("value"));
The value is returned correctly in 1.2.6
Upgrading to 1.3.1 resulted in a returned value of "undefined"
Attachments (0)
Change History (6)
Changed February 03, 2009 02:11AM UTC by comment:1
Changed February 03, 2009 10:41PM UTC by comment:2
It is being served up as application/xml+xhtml.
If the alert is set to fire after information has been entered into the input field, that's when the error is produced in 1.3.1. In 1.2.6, the value inputted into the field is displayed.
Changed February 03, 2009 10:52PM UTC by comment:3
Firefox, Chrome, Safari and IE7 all behaved the same with regards to this bug.
Changed February 04, 2009 12:15AM UTC by comment:4
| owner: | → john |
|---|
Changed May 10, 2009 03:18AM UTC by comment:5
| owner: | john |
|---|
Can you attach a test case? I just can't make this bug happen.
Changed August 09, 2009 12:58AM UTC by comment:6
| resolution: | → worksforme |
|---|---|
| status: | new → closed |
I can't repro this and the OP didn't provide a test case.
It seems to return an empty string in both versions for me. Is there a particular browser that returns the incorrect value?
Are you serving up this document as application/xml+xhtml ? I wonder if that might cause it to return undefined, or whether it's significant that the markup has no value attribute.