Joey Arhar

I opened a bug here: https://bugs.chromium.org/p/chromium/issues/detail?id=1025893 Please star the bug to help the DevTools team prioritize this issue

Yes, it maybe could be fixed by my change. Does this puppeteer version include the breaking change?

I filed a bug to limit the number of console messages: https://bugs.chromium.org/p/chromium/issues/detail?id=1340037 Does 1,000 console messages max sound like a good number?

Ok, I am making the change in chromium with 500 as the max number of messages

> Elements that trigger a script-executing side effect due to insertion or removal need to do so using some kind of queue if we ever want to remove mutation events...

Is the goal here simply to remove mutation events? Based on [tkent's doc](https://docs.google.com/document/d/1vYBKZGjE-EEFHy-sidffEqKNxuBSENcym3ql-3jDYfk/edit#) I found in https://github.com/whatwg/dom/issues/305, it sounds like we would already have to contact sites to get them...

> - Inserting an inline (one without src) runs the script text in it immediately, before the insert call returns. > - Inserting an iframe with no src attribute set...

Thanks for writing this up! It sounds like moving elements around within the same parent without clobbering state could be a huge win! I'm interested to hear what the react...

@sebmarkbage @marvinhagemeister @developit I sort of already asked in [this comment](https://github.com/whatwg/html/issues/5484#issuecomment-670188978), but would @isiahmeadows's suggestion here of not clobbering state when moving around nodes within one parent solve react's and...

> I would also like to see some more rationale as to why an arbitrary move (with both parents sharing a common root) is less feasible. What are the particular...