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

That seems like an API you can build yourself. Write the instruction stream to an array in the worker, then read it back out in the main thread and execute the DOM operations. You can schedule the work with requestIdleCallback, setTimeout and requestAnimationFrame.

Also to go back to @dherman's comment, I'm not convinced we need DOM mutation transaction semantics like this. I do think we need a way to spread the style, layout and paint steps inside the browser out over several frames. I'm not convinced that doing that requires building an integer based abstraction over the DOM, that certainly doesn't match any existing implementation and doesn't feel like a primitive. It's more like a library you can write yourself.

---
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-227516552