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

Note that either support self-closing or void elements DO require a parser change. The cost isn't so much about updating the parser but it's that every HTML parser implementation in the world would have to update the parser or else we'd get XSS vulnerability everywhere :( Not saying it's impossible or it's a bad idea but the cost isn't just in the web browser but everything that touches the HTML content in general.

-- 
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-502309229