Re: [w3c/webcomponents] Custom 'void' or self-closing elements (HTML parser changes) (#624)

The problem with this specific issue is that it mixes **custom void**
elements and **custom self-closing** elements. The issue should be split it
two, because the main argument against here is difficulty of parser
modification, and the modification varies greatly between:

1. - void elements - <my-element> - for which parser modification is hard,
because it requires tracking the type of the tag and potential content
inside
2. - self-closing - <my-element/> - parser modification is easy requires,
because it only requires tracking of the closing sequence **/>**

Other consideration is that HTML parser is HTML aware and should not be
treating <p> and legacy elements the same way as custom elements, so the
legacy elements should be out of scope as well.


-- 
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/624#issuecomment-502018751