Re: [w3c/webcomponents] HTML parser: align custom elements with the template element (#630)

Promise, last comment on this (tonight) :P 

The spec for `<p>` says it will allow following as child elements:
```
a, audio, del, ins, map, noscript, or video element, or an autonomous custom element.
```
The last bit about custom elements is interesting, since *in practice*, most custom elements act like blocked elements like div, figure, etc which it explicitly doesn't allow. Not sure about the reasoning of including custom-elements in the <p> tag, where it explicitly is pretty restrictive otherwise. I can see why it should reject CEs because there's no way of knowing what the custom-element should be and should it even be allowed as a paragraph content. 

There would have been no major issues if the custom element was rejected and the `p` tag would close like it does with `div`s. 


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/630#issuecomment-534906435