Re: Resending: DOMCharacterDataModified:prevValue?

FWIW, WebKit has avoided adding DOMAttrModified for this reason.
https://bugs.webkit.org/show_bug.cgi?id=8191

A replacement would be great. MutationEvents are awful. Jonas, my memory is
that your suggestion for a replacement was relatively well-received, no? Is
there a final draft of that somewhere?

On Thu, Jul 1, 2010 at 3:36 PM, Jonas Sicking <jonas@sicking.cc> wrote:

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