I'm pretty sure we already have a bug on this (it's fixed for <input>, but not <textarea>).
This testcase is a bit complex (less is more), but i think things work as designed. When the value of a <textarea> or <input> is changed only the .value is changed. The childnode or the DOM-attribute will remain unchainged and thus reflect the .defaultValue of the form-element. This is what the DOM spec says to do at least for <input>. For <textarea>s the behaviour isn't defined, but we desided to let them behave the same for consistency.
Status: NEW → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.