W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2014

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

From: <bugzilla@jessica.w3.org>
Date: Tue, 08 Apr 2014 07:19:14 +0000
To: public-webapps@w3.org
Message-ID: <bug-25290-2927@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25290

            Bug ID: 25290
           Summary: [Custom]: Ban uppercase and leading "xml" in custom
                    element names?
           Product: WebAppsWG
           Version: unspecified
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Component Model
          Assignee: dglazkov@chromium.org
          Reporter: simonp@opera.com
        QA Contact: public-webapps-bugzilla@w3.org
                CC: mike@w3.org, public-webapps@w3.org
            Blocks: 14968

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).

http://www.whatwg.org/specs/web-apps/current-work/multipage/elements.html#embedding-custom-non-visible-data-with-the-data-*-attributes 
http://www.whatwg.org/specs/web-apps/current-work/multipage/the-iframe-element.html#the-embed-element

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.

I guess leading "xml" is reserved by XML Core WG.

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.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Tuesday, 8 April 2014 07:19:16 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:23 UTC