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.

This is the whole problem. I should be able to build off of html as a format, and have those extensions be first class, not some weird tacked on thing. They are custom elements from the BROWSERS point of view, not the documents point of view. All the good things about HTML come from it being a semantic data format. Sometimes I need more semantics than the built-in set, and I should be able to add a tag to represent those, with a semantic name. 

The JS custom element thing is just display logic. And view should be written to conform to the model not the other way around. 

I suggest the "nice folks over at whatwg/html" put the elements *they* make in a namespace, and let me have the default one. 

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

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