smaug----

I think this is fine. https://issues.chromium.org/issues/400758510 is interesting. That was filed immediately when someone tried to use the API. That is more for the HTML part of the feature though....

There are so many different ways to schedule things that handling all the options in a param of addEventListener might be tricky. (For example, how to schedule running during idle...

I agree with bz. We need to do this per property, not all at once. And while doing it, it is possible that we figure out the merge isn't really...

ctor for Document is already shipping. I would just do "Document, HTMLDocument and XMLDocument", since that requires least changes to the implementations and be done with this issue. Needs of...

I'm still hoping we actually try to get rid of mutation events. Isn't Firefox still the only browser warn about their use. (FYI, Firefox telemetry compares Window objects, in which...

Yeah, I like the concept of composed tree, and at least in Gecko we very much have that, especially in the form of composed document (composed tree which has Document...

> Two of the APIs are available on Range as `deleteContents()`, `extractContents()`, but using Range, even StaticRange, is slower than implementing these operations in JS. Curious, do you have some...

Someone mentioned uncomposed earlier today, but I couldn't find any current use of that. I could live with that anyhow. (but I still don't like legacy. It hints that something...

Maybe I could live with that though the legacy part seems not really important there, it is uncomposed which tells what the thing is about. If the old thing is...

I said I can live with that even though I disagree with you why it is or it is not needed. (IMO, it doesn't add any useful value if we...