[Bug 25290] [Custom]: Ban uppercase and leading "xml" in custom element names?

https://www.w3.org/Bugs/Public/show_bug.cgi?id=25290

Ryosuke Niwa <rniwa@webkit.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |rniwa@webkit.org

--- Comment #2 from Ryosuke Niwa <rniwa@webkit.org> ---
(In reply to Simon Pieters from comment #0)
> http://w3c.github.io/webcomponents/spec/custom/#dfn-custom-element-type
> 
> HTML has two sets of open-ended attribute names which have more
> restrictions: can't contain ASCII uppercase and can't begin with "xml"
> (ASCII-case-insensitively).
>
> I guess leading "xml" is reserved by XML Core WG.

That sounds reasonable.

> The ASCII uppercase is because the HTML parser and some DOM APIs case-fold
> to lowercase so using uppercase in the actual name means trouble.
> 
> We could also require for element names that the first character is [a-z]
> since the HTML parser will not parse something into an element otherwise.

So are these requirements.

(In reply to Anne from comment #1)
> I disagree with this. We should not enforce constraints that are not
> violations of namespace well-formedness (if we even should enforce those).

Do you think there are use cases that are harmed by adding restrictions like
this?  Do you think people would like to use uppercases in element names,
etc... in practice?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Tuesday, 8 April 2014 23:27:11 UTC