Re: [whatwg/dom] Proposal: DOMChangeList (#270)

> Can we separate these into two distinct proposals - one for async application of layout and another for DOM mutations on worker threads?

How would you feel about an effort to identify the lowest layer of DOM operations that is sufficient to describe the higher layering of just creating and mutating the DOM data structure that is used in DOM1-4? (Some of the work that Chrome has done in its extension's support for Isolated Worlds feels like it overlaps with the constraints here.)

That subset would then be a natural starting point for tree construction and mutation operations that could be transferred across a worker boundary (and could be decoupled from the more controversial effort to reduce the need to use garbage-collected JavaScript objects to represent the intermediate states).

---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/dom/issues/270#issuecomment-227618284