From: Anne van Kesteren []

> I think the problem is that nobody has yet tried to figure out what invariants
> that would break and how we could solve them. I'm not too worried about
> the parser as it already has script synchronization, but cloneNode(), ranges,
> and editing, do seem problematic. If there is a clear processing model,
> Mozilla might be fine with running JavaScript during those operations.

Even if it can be specced/implemented, should it? I.e., why would this be OK 
where MutationEvents are not?

Reply via email to