Philip Jägenstedt

@annevk do you think there's implementer interest from WebKit?

The root cause of this is a change in Chrome, https://crbug.com/41451306, to include custom properties in the result of `getComputedStyle()`. This is a change we'd like to make as there's...

This change is rolling out again in Chrome 141, tracked by https://chromestatus.com/feature/5070655645155328. The workaround suggested above has been verified as working on one site that tried it, so it's what...

@zcorpan do you want to review as well? It touches some things you've worked on I think.

I've made some additional changes but things don't quite make sense yet. The direction I'm heading in is: - When the parser encounters an `` element, it doesn't insert it....

I've now rewritten a lot of this to make it match my previous comment, and I think it's in good enough shape for review now. I left two inline issues:...

Okay, should that state be sticky, or what happens if the nodes later realign so that the check passes?

I've given some thoughts to error handling for `contentmethod=prepend`. Here's an example of the problem: ```html will be removed this element is inserted window.refnode = document.getElementById('refnode'); refnode.remove(); reference node is...

> Applying patches inside the fragment parser (e.g. `innerHTML`) should be guarded in the same way as declarative shadow root, to avoid breaking assumptions made by userland sanitizers like DOMPurify....

This was discussed in https://github.com/whatwg/html/issues/11622 today. There's more httparchive research to be done to understand the compat risk, and @zcorpan has an export of httparchive results to look at now.