This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 21200 - [Custom]: Case sensitivity of custom element names?
Summary: [Custom]: Case sensitivity of custom element names?
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - Component Model (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Dimitri Glazkov
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
: 21889 (view as bug list)
Depends on:
Blocks: 14968
  Show dependency treegraph
 
Reported: 2013-03-05 20:06 UTC by William Chen
Modified: 2013-06-19 21:32 UTC (History)
2 users (show)

See Also:


Attachments

Description William Chen 2013-03-05 20:06:41 UTC
"NAME, the custom element name of the element being registered"

The HTML namespace is case insensitive but the SVG and XHTML namespace is not. How should we treat case for custom element names? A few options on the top of my head are:

1. Make names case sensitive. This would causes a bit of weirdness because the name custom-Foo could be registered but useless in the HTML namespace because it contains a capital letter.

2. Make names case insensitive. This would also cause weirdness in SVG and XHTML because custom-Foo and custom-foo could not both be custom elements even though they would be different types of elements.

3. Make names case sensitive if it "inherits" from SVGElement and case insensitive if it "inherits" from HTMLElement, but this causes increased complexity and still causes weirdness for XHTML.
Comment 1 Dimitri Glazkov 2013-04-22 22:08:46 UTC
Can we define this in terms of the type of document we're in? If we are in HTML document, custom element names are case-insensitive. Otherwise, they aren't. WDYT?
Comment 2 Dimitri Glazkov 2013-05-07 19:38:19 UTC
*** Bug 21889 has been marked as a duplicate of this bug. ***
Comment 3 Dimitri Glazkov 2013-05-07 20:55:55 UTC
https://dvcs.w3.org/hg/webcomponents/rev/24a11e328f62
Comment 4 Dimitri Glazkov 2013-05-30 22:30:38 UTC
I will break this when fixing bug 21958, will need to re-fix again.
Comment 5 Dimitri Glazkov 2013-06-19 21:32:16 UTC
https://dvcs.w3.org/hg/webcomponents/rev/d6f371c89870