This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/the-button-element.html Section: http://www.whatwg.org/specs/web-apps/current-work/#the-textarea-element Comment: Setting .value on a textarea should set the dirty flag to true Posted from: 67.111.52.130 User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.2a1pre) Gecko/20110328 Firefox/4.2a1pre
*** Bug 12424 has been marked as a duplicate of this bug. ***
In particular, this happnes for text inputs, but not textareas. The inconsistency seems wrong to me.
I don't see in the spec where it says that setting .value should set the dirty value flag for input.
http://www.whatwg.org/specs/web-apps/current-work/multipage/common-input-element-attributes.html#dom-input-value in the "value" section says: On setting, it must set the element's value to the new value, set the element's dirty value flag to true ...
Ah yeah, sorry.
Turns out WebKit doesn't do this, and nor does IE. But Gecko and Opera do it, so I'm sold! Wow is there poor interop on this. You'd think this test would be simple: http://junkyard.damowmow.com/471 ...but four browsers, four results. EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Accepted Change Description: see diff given below Rationale: Concurred with reporter's comments.
Checked in as WHATWG revision r6241. Check-in comment: Make textarea and input consistent. (Interop here is a disaster currently, so we can change this with impunity.) http://html5.org/tools/web-apps-tracker?from=6240&to=6241
> Turns out WebKit doesn't do this Current WebKit does, actually; see https://bugs.webkit.org/show_bug.cgi?id=57636 > nor does IE. Odd. IE seems to do it in my testing. > But Gecko and Opera do it Opera is sort of weird: it treats users typing and .value sets differently for textarea (the only browser to do that, as far as I can tell). See https://bugs.webkit.org/show_bug.cgi?id=57636#c5 > ...but four browsers, four results. Fwiw, current dev Chrome and current Firefox agree on that testcase, since that WebKit bug was fixed. So only 3 results now! ;) Though actually it's still 4, because IE9 Standards mode does one thing, while IE9 in IE8, IE7, and compat modes does something else.... We'll get to interop sometime, I'm sure. Thanks for making the change!
mass-move component to LC1