Closed
Bug 32795
Opened 24 years ago
Closed 24 years ago
DOM sees old value in textarea after changing the value
Categories
(Core :: DOM: Core & HTML, defect, P3)
Core
DOM: Core & HTML
Tracking
()
VERIFIED
FIXED
M16
People
(Reporter: jcarpenter0524, Assigned: jst)
Details
(Whiteboard: [nsbeta2+])
Attachments
(2 files)
Overview Description: If you use DOM to change the value in a textarea, then look at that value, DOM still sees the old value Steps to Reproduce: - see testcase Actual Results: DOM sees "default value 1" as the value of the textarea Expected Results: DOM should see "fun fun fun" as the value of the textarea Build Date & Platform Bug Found: All platforms 2000-03-21-06
Reporter | ||
Comment 1•24 years ago
|
||
Comment 2•24 years ago
|
||
Please identify ASAP any known high-profile sites that depend on this. Thanks, Jim
Reporter | ||
Comment 4•24 years ago
|
||
adding beta2 keyword, and removing pdt status
Keywords: beta2
Whiteboard: [PDT-]
Comment 6•24 years ago
|
||
This problem actually appears to be that getAttribute('value') and .value don't agree on the same value. Browsing through the code, it is probably because nsHTMLTextAreaElement::SetValue (in layout) does not call SetAttribute and thus setting .value has only a visible effect without changing the underlying property. (Then again, I don't fully understand the code) Attached a new testcase demonstration the difference between getAttribute and .value
Comment 7•24 years ago
|
||
Assignee | ||
Updated•24 years ago
|
Status: NEW → ASSIGNED
Target Milestone: --- → M16
Fwded to rickg to get his opinion on PR2 stopper here.
Whiteboard: [NEED INFO]
Assignee | ||
Comment 10•24 years ago
|
||
I just checked in a fix for this, marking FIXED.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Updated•5 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•