Re: [WICG/webcomponents] Why do we really need hyphens? (#658)

> The lack of hyphens in custom element names is simply a contract between the nice folks over at whatwg/html and us site developers that the tags they make and the tags we make are in a different space; thus ensuring a tag you make today isn't going to conflict with an official element added later on.

You could still have that contract **_and_** allow custom elements without hyphens.  Anyone who wants the safety of the contract would use hyphens, and anyone who wants to take their chances could do without them.

But let's consider what the worst thing is that could happen:  if I introduce (for example) a `<string>` custom element, and use it, and then an official `<string>` element is added to browsers, my site continues to use my custom element instead of the new official element (since custom elements should always override official ones!)  How is that bad?  Everything continues to work as I expect.  I don't see any downsides at all.

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

Message ID: <WICG/webcomponents/issues/658/1546767686@github.com>