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

oelmekki left a comment (WICG/webcomponents#624)

>  Deciding not to go with self-closing custom elements actually benefits the user, for all the reasons already mentioned in this thread.

I have of course read the whole thread before commenting, and I don't see where you're getting that from. Beside the argument that "yeah, but doing that would require changes" (since when did we decide the web should never change? why exactly are browsers pushing updates every week, then?), the only maybe valid argument was that it would introduce XSS vulnerabilities, but when the author of that claim was asked to explain it, they never commented again (unless I missed something). What I *did* see, though, is an overwhelming majority of people expressing support for self-closing custom elements.

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

Message ID: <WICG/webcomponents/issues/624/2884853909@github.com>