This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 12423 - Setting .value on a textarea should set the dirty flag to true
Summary: Setting .value on a textarea should set the dirty flag to true
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
: 12424 (view as bug list)
Depends on:
Reported: 2011-04-05 14:24 UTC by contributor
Modified: 2011-08-04 05:14 UTC (History)
6 users (show)

See Also:


Description contributor 2011-04-05 14:24:17 UTC

Setting .value on a textarea should set the dirty flag to true

Posted from:
User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.2a1pre) Gecko/20110328 Firefox/4.2a1pre
Comment 1 Boris Zbarsky 2011-04-05 14:26:09 UTC
*** Bug 12424 has been marked as a duplicate of this bug. ***
Comment 2 Boris Zbarsky 2011-04-05 14:26:46 UTC
In particular, this happnes for text inputs, but not textareas.  The inconsistency seems wrong to me.
Comment 3 Simon Pieters 2011-04-05 14:42:05 UTC
I don't see in the spec where it says that setting .value should set the dirty value flag for input.
Comment 4 Boris Zbarsky 2011-04-05 14:47:42 UTC 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 ...
Comment 5 Simon Pieters 2011-04-05 14:51:32 UTC
Ah yeah, sorry.
Comment 6 Ian 'Hixie' Hickson 2011-06-16 18:03:31 UTC
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:

...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:

Status: Accepted
Change Description: see diff given below
Rationale: Concurred with reporter's comments.
Comment 7 contributor 2011-06-16 18:03:53 UTC
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.)
Comment 8 Boris Zbarsky 2011-06-16 18:47:19 UTC
> Turns out WebKit doesn't do this

Current WebKit does, actually; see

> 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

> ...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!
Comment 9 Michael[tm] Smith 2011-08-04 05:14:17 UTC
mass-move component to LC1