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

@rniwa
Could you, or someone else, please explain how adding support for self-closing elements, i.e. `<foo/>`,  would actually introduce an XSS vulnerability? - preferably with an example.

Maybe I'm missing something, but I don't see a problem here - and I'm probably not alone  :-)

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

Received on Thursday, 4 July 2019 14:02:39 UTC