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

I don't exactly what you mean by you want to scope custom elements. They already are in the sense that custom elements are only available if you define them in *your* document. Scoping them per-shadow root seems a bit overkill imo as custom elements seem like they were more designed for the main document but every developer is free to do as they please. Which wraps back to the hyphen issue. The web as it stands right now is all about forwards compatibility. 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 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-341865653