Re: [whatwg/dom] [discussion] Async nature of MutationObserver can cause room for error? (#399)

The problem with a synchronous library is that you can then put the browser in a state of it not knowing what's going on. We used to have that and mutation observers are the replacement as it caused all kinds of problems.

With mutation observers the code that you write needs to be a little more involved. You get the changes from the API and you need to figure out if you just get the state from the tree instead or use the changesets in some way.

-- 
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/399#issuecomment-272813492