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

I think you're still misunderstanding me.  What I'm saying is that there should be one definition in one spec which defines what valid name means for HTML documents, which may refer to XML spec, and defines a set of valid names for HTML parser, XML parser, createDocument in HTML documents, and createDocument in XML documents.  Hopefully there aren't many discrepancies between them but as you noted, they can't all be the same.

Now, if there is a known definitely safe subset of all those four potentially distinct sets that we can use for custom elements, then I'm all for it. But it sounded like there isn't, or they aren't even well defined yet.  So it seems that we need to do the exercise of determining those four sets first before expanding the set of valid names allowed in custom elements

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