Re: [webcomponents] [Custom]: "are" custom element names ASCII characters, or MUST they be ASCII characters? (#239)

I went with a liberal-as-possible intersection set in https://github.com/w3c/webcomponents/commit/35086b3d4c67d92461445dfb5a9d33f99ff574a0. See https://w3c.github.io/webcomponents/spec/custom/#valid-custom-element-name for the rendered output.

We can work toward centralizing all definitions into one place (presumably DOM) later, and I think they will indeed all be distinct, but the definitions are already out there. I guess either DOM or browsers have a bug since DOM specifies XML 5th edition and browsers use XML 4th edition for createElement(NS). But for now custom elements will just use XML 5th edition like DOM does, and if we want to change both at once to align with browser reality (instead of making browsers more liberal) we can definitely do so.

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/webcomponents/issues/239#issuecomment-193956616