Properly apply pending DOM changes when a transaction is dispatched #9
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Right now, if the view is updated precisely between the point where DOM changes happen and the point where the mutation observer is called, those DOM changes are ignored. It is possible to store them and apply them after the update (mapping the change objects) though, so that's what we should do.
Due to the way mutation observers call their callbacks (in a microtask), dispatching a transaction with dom changes pending is not actually something that can happen during sensible use (you'd have to have caused those changes in the same task that dispatched the transaction), so I've decided this is too much extra code for no concrete gain, and discarding such DOM mutations is okay.