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 20823 - [Custom]: Section 3 (Terminology), custom element name
Summary: [Custom]: Section 3 (Terminology), custom element name
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - Component Model (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Dimitri Glazkov
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 20684
  Show dependency tree / graph
 
Reported: 2013-01-30 06:57 UTC by Morrita Hajime
Modified: 2013-01-30 23:54 UTC (History)
0 users

See Also:

Attachments

Description Morrita Hajime 2013-01-30 06:57:28 UTC 
> "The custom element name identifies a custom element and is a sequence of alphanumeric ASCII characters"

The name should be a subset of valid HTML element name.
Reading only this statement, something like "0" or "-foo" can be valid names.

Editorial nit pick: The title of section 3 doesn't have its bullet number.
Comment 1 Dimitri Glazkov 2013-01-30 19:28:18 UTC 
I probably need to make it a Name production.http://www.w3.org/TR/xml/#NT-Name
Comment 2 Dimitri Glazkov 2013-01-30 23:54:23 UTC 
https://dvcs.w3.org/hg/webcomponents/rev/9f8ec3f8f97e