W3C home > Mailing lists > Public > whatwg@whatwg.org > November 2011

[whatwg] Automatic transaction should support changing the value of input/textarea

From: Jonas Sicking <jonas@sicking.cc>
Date: Sun, 27 Nov 2011 22:13:08 -0800
Message-ID: <CA+c2ei9Mm-S9rSq0jGbPQ6_5qt0cZLaGdoD6VKD1AZ1Sz0z-nQ@mail.gmail.com>
On Sat, Nov 26, 2011 at 6:57 PM, Ryosuke Niwa <rniwa at webkit.org> wrote:
> On my second thought, it's probably okay to require UAs to always restore
> the entire value because the only cause where UA needs to store the old data
> is when the script sets the value in automatic transaction, and it doesn't
> impose new burdens on UAs in any other situations since scripts can't access
> the shadow DOM of native input/textarea implementations.
>
> Alright, I think I'd just say that assignment to value should be revertible
> unconditionally so as long as input and textarea exist.

Another option is to say that if the textarea value is any other value
than the "after" value when a automatic transaction is undone, it
doesn't do anything. One fairly simple way to do this would be to
store a hash of the "after" value and compare that to a hash of the
current value. If the two doesn't match up then undoing the
transaction would do nothing.

This allows the implementation to store far less data for each
transaction. If computing the hash is a concern, then the
implementation could simply store the whole value which is no worse
than what the above requires.

There are other solutions too, which require monitor *all* mutations
that happen to a text node outside of automatic transactions, but they
are likely too complex to implement.

/ Jonas
Received on Sunday, 27 November 2011 22:13:08 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:38 UTC