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

> https://github.com/w3c/webcomponents/issues/624#issuecomment-385341368
> ... There's basically only interest in security fixes and non-normative changes.

> https://github.com/w3c/webcomponents/issues/624#issuecomment-385347171
> So people are doomed to double their simple `<custom-element></custom-element>` names till the end of internet?

> https://github.com/w3c/webcomponents/issues/624#issuecomment-385356383
> As far as the `text/html` format goes that's where we're at.

@annevk Sorry, but I simply cannot accept this.

This is a very real problem for those of us who write large web apps, and something that causes quite a bit of daily frustration, wasted time, and bloated code.

The ergonomics of a language matters, and saying we just have to live with it because you do not feel like _ever_ evolving the language in any way, that's just plain unacceptable to me.

Please either provide a valid reason why `<foo/>`, which as I understand it is currently invalid, can't simply be interpreted as `<foo></foo>` - or reopen this issue so we can have some actual progress.

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