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

@trusktr: Although I don’t think your specific idea is easily feasible (and also, I don’t think preventing elements like `<meta>`, `<link>`, `<br>` from having self‐closing tags actually helps with anything at all), I do agree that it makes sense to wish for a fresh new HTML parsing mode that removes certain struggles from authors. Anne’s “XML 5” idea seems like a more sensible approach.

On the other hand, however, I really don’t think it’s actually going to happen any time soon, if ever at all. It seems that implementors are consistently really sceptical of changing parser behavior, mostly because of difficult security analysis that needs to be made on their implementations.

In addition, of course, is the very difficult implied questions of “What about APIs such as `.innerHTML`?” Should those APIs keep the old parser behavior, or should they reflect the new parser mode? Note that a lot of existing libraries might expect the old parser behavior, and break (perhaps in subtle ways) if it’s different.

There is very little ergonomic benefit in changing the parser now, compared to all the potential problems and questions that arrive from it.

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