- From: Matthew Dean <notifications@github.com>
- Date: Wed, 01 Nov 2017 17:32:20 -0700
- To: w3c/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Thursday, 2 November 2017 00:32:43 UTC
IMHO the requirement of hyphenated names for custom elements is like requiring underscore-prefixed variables names in JavaScript in order to declare `const`. And the namespacing-collision thing is kind of the same argument. I'm sure it's possible there were JS libraries who declared `Map` as an object name before that was introduced, yet there's no restriction there on what people can call things because of collision fear. The convenience of hyphen-less elements greatly outweighs the down-the-road concern that some element with the same name will be introduced. I agree it's part of what makes Vue so easy-to-use and keeps templates concise. -- 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/658#issuecomment-341283609
Received on Thursday, 2 November 2017 00:32:43 UTC