Re: [whatwg/dom] shadowRoot.innerHTML parsing elements from another realm/iframe (#977)

> From what I remember when we discussed this during the F2F meeting, @mfreed7 mentioned that one possible explanation for the current behavior in chrome could be attributed to the customization of built-ins, in this case, the customization of the `<p>` element. He initial reaction (from what I can remember) was that this could be fixed to have a consistent behavior between the `<p>` and the custom element, which seems to be behaving correctly in all browsers, meaning the `<p>` should be created from the main window.

I don't understand that. There are many ways to interpret or even misread the spec but creating customized built-ins and autonomous custom element from two different realms during a fragment parsing algorithm ain't one of them.

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