Re: [whatwg/dom] Node insertion step 7.7 isn't upgrading disconnected uncustomized elements that browsers do upgrade (#833)

All these test cases involve parsing, so it's conceivable that browsers are actually doing the right thing on the insertion and the wrong thing is when they're parsing the HTML fragment. 

If it's happening during the fragment parsing, rather than during the insertion: https://html.spec.whatwg.org/multipage/parsing.html#parsing-html-fragments tells us to parse into a new document instead of the browsing context one, and https://html.spec.whatwg.org/multipage/custom-elements.html#look-up-a-custom-element-definition tells us not to customize elements if the document has no browsing context, so if a custom element is created in fragment parsing one of those is off.

-- 
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/833#issuecomment-585725532