On Thu, Jul 16, 2015 at 6:03 PM, Domenic Denicola <d...@domenic.me> wrote:
> Ah OK, thanks. Is there any way to get a consensus from Mozilla as a whole, 
> preferably ahead of the F2F?

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.

I've been a bit too occupied with Fetch et al to put in the hours
myself ahead of the meeting.


Reply via email to