This PR addresses a class of issues where if multiple mutations occurred in a single tick (e.g. append an element to multiple parents one after the other) they could cause errors in the ObservableDOM handling because the inferred state from a single mutation would conflict with the handling of a subsequent mutation.
This is a complication that is tracked in #100.
This PR also adds tests to avoid regressions on this behaviour and integration tests that assert the state of the client NetworkedDOMWebsocket match the state of the server document NetworkedDOMDocument
What kind of changes does your PR introduce? (check at least one)
[x] Bugfix
Does your PR introduce a breaking change? (check one)
[x] No
Does your PR fulfill the following requirements?
[ ] All tests are passing
[x] The title references the corresponding issue # (if relevant)
Fixes #176.
This PR addresses a class of issues where if multiple mutations occurred in a single tick (e.g. append an element to multiple parents one after the other) they could cause errors in the
ObservableDOMhandling because the inferred state from a single mutation would conflict with the handling of a subsequent mutation.This is a complication that is tracked in #100.
This PR also adds tests to avoid regressions on this behaviour and integration tests that assert the state of the client
NetworkedDOMWebsocketmatch the state of the server documentNetworkedDOMDocumentWhat kind of changes does your PR introduce? (check at least one)
Does your PR introduce a breaking change? (check one)
Does your PR fulfill the following requirements?