Philip Jägenstedt

This is speculative editing following https://github.com/whatwg/html/issues/11669#issuecomment-3589383629 to see what it would mean to remove the inert document from the HTML fragment parsing algorithm. There are two questions, one small and...

> I think I agree this is what we need to do, but I don't want to lose sight of the requirements for `streamHTML()` (and `setHTML()`) while we do this....

The seems like a duplicate of https://github.com/bubkoo/html-to-image/issues/542. I'll comment there with a possible workaround.

@DigiTec, could you help us find a good contact for this issue in Edge?

Does anyone have a high level view of when browsers block painting and for what reasons? I assume it's a non-interoperable pile of heuristics, but it's part of the reality...

This doesn't work yet, but uploading just to confirm the desired behavior. From my reading of Blink, this flag is disabled for `innerHTML`, `outerHTML`, `insertAdjacentHTML()`, and `createContextualFragment()` unless trusted types...

As an editorial matter, I think I'd like the "Each HTML parser has a something flag" style, but I didn't make that change yet.

If it doesn't depend on TT it's even simpler, basically the "legacy" HTML setting methods don't get declarative shadow roots and in every other context they're enabled. Tests are needed...

A test for this would be: ```html Media Loading State: the :buffering and :stalled pseudo-classes // The order of "is currently stalled" changing and events firing changed in // https://github.com/whatwg/html/pull/11959....

I've written a test using a custom Python handler in https://github.com/web-platform-tests/wpt/pull/56562 now, it first sends 10 seconds of data and then waits, causing the stalled event to fired. Once fired,...