W3C home > Mailing lists > Public > www-dom@w3.org > July to September 2010

Re: Resending: DOMCharacterDataModified:prevValue?

From: Jonas Sicking <jonas@sicking.cc>
Date: Thu, 1 Jul 2010 15:36:45 -0700
Message-ID: <AANLkTinRfme07P4iTkdprwLMXmeE9E0WGDh2zspucxOj@mail.gmail.com>
To: Travis Leithead <travil@microsoft.com>
Cc: "www-dom@w3.org" <www-dom@w3.org>, Doug Schepers <schepers@w3.org>, "Olli@pettay.fi" <Olli@pettay.fi>
Personally I would recommend that you don't implement
DOMCharacterDataModified. The mutation events are very hard to get
right in all edge cases. We'd be much better off coming up with a
replacement than having all browser implementations chasing down edge
cases forever.

/ Jonas

On Thu, Jul 1, 2010 at 3:19 PM, Travis Leithead <travil@microsoft.com> wrote:
> DOMCharacterDataModified event—should it provide a “prevValue” and
> “newValue”? The definition of the event [1] seems to indicate “no” (which is
> what other browsers have implemented), but the definition of [2] “prevValue”
> and “newValue” seem to contradict that.
>
>
>
> The third IE9 platform preview [3] is currently supporting supplying the
> prevValue/newValue, but at a large performance cost. I’d like to see this
> apparent contradiction resolved one way or the other. Thanks!
>
>
>
> -Travis
>
>
>
> [1]
> http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html#event-type-DOMCharacterDataModified
>
> [2]
> http://dev.w3.org/2006/webapi/DOM-Level-3-Events/html/DOM3-Events.html#events-Events-MutationEvent-prevValue
>
> [3] http://ie.microsoft.com/testdrive/Default.html
>
>
Received on Thursday, 1 July 2010 22:37:41 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 22 June 2012 06:14:04 GMT