Re: [whatwg/dom] MutationObserver callbacks happen in wrong order. (Issue #1105)

Maybe there's actually a bug in the browser implementation (or the spec)? Regarding these two lines:

```js
 t.remove() // queue mutation for two
 one.append(t) // queue mutation for one
```

Shouldn't the reaction for `#two` run before the reaction for `#one`, because the `t.remove()` call modifies the children of `#two` so at that point the MO for `#two` should be queued. Then the `one.append(t)` line should queue the MO for `#one`.

So why, in this case, is `#two`'s MO firing after `#one`'s?

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

Message ID: <whatwg/dom/issues/1105/1229119402@github.com>