Re: Resending: DOMCharacterDataModified:prevValue?

On Tue, Jul 13, 2010 at 8:34 AM, Ojan Vafai <ojan@chromium.org> wrote:
> 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?

No, but I would love to find time to create one. I can try to write up
a updated proposal, but I don't think I'll have time to be editor of a
spec. If we can get agreement on this though, it's possible that we'll
be able to put an implementation into Firefox 4, at which point we'd
likely start putting warnings in the developer console any time
someone registers listeners for mutation events, and hopefully remove
the mutation event feature from the firefox version after 4.

/ Jonas

Received on Tuesday, 13 July 2010 18:55:26 UTC