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

@annevk Just speaking for myself but I'm sure others would like it too but I'd certainly find self-closing tags an improvement and assuming only `<x-foo />` form is allowed (initially at least) it shouldn't conflict with `<p>` like behaviours which I feel should be a separate issue given that it's far more complicated.

And from what I'm aware isn't it the case that a correct parser should consider this an error anyway `<x-markdown />` (assuming this still applies https://www.w3.org/wiki/Validating_your_HTML#Different_browsers_interpret_invalid_HTML_differently) so correct parsers shouldn't break (just fail) if given `<x-markdown />`, the thing is the addition of virtually anything to HTML could potentially make the HTML parser a source of bugs, e.g. simply adding another void tag or auto-closing (like <p>) would mean existing parsers would be invalid (and plenty of other things I'm sure). For those reasons I'm definitely not happy with the argument that we can't extend HTML because some parsers might break.

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