[whatwg] DOM Range: redefining behavior under DOM mutation
Simetrical+w3c at gmail.com
Wed Mar 30 13:23:52 PDT 2011
On Wed, Mar 30, 2011 at 2:48 PM, Boris Zbarsky <bzbarsky at mit.edu> wrote:
> The spec we're looking at is
> as of March 26, I assume? This spec is all kinds of broken if you allow
> userdata handlers and mutation events.
Oh, whoops. That's what I forgot about. Ryosuke Niwa of WebKit says
that for editing commands, DOM mutation events for editing commands
(not sure about things like insertBefore()) get delayed until after
the command finishes executing:
But I'm not too happy trying to spec anything interesting here when
you have this DOM mutation stuff hanging around, so for now I think
I'll just spec what DOM 2 Range says. I'll leave a note in the spec
to revisit this later.
> Ah, I misunderstood what the result was. Let me look up what Gecko actually
> does here and get back to you.
More information about the whatwg