-
Notifications
You must be signed in to change notification settings - Fork 378
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Define valid custom element name more rigorously
This defines a valid custom element name with a grammar, as is done for the XML definitions that createElement(NS) uses. This closes #239 by taking the following fairly liberal intersection: - Allowed in createElement - Allowed in createElementNS - Initial [a-z] required for HTML parser compatibility - Hyphen required - Uppercase characters disallowed - Blacklist disallowed Also, clean up how the spec talks about the two types of custom elements (custom tags and type extensions).
- Loading branch information
Showing
2 changed files
with
54 additions
and
31 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters