- From: <bugzilla@jessica.w3.org>
- Date: Thu, 20 Nov 2014 10:09:16 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20973 --- Comment #10 from Deepak Singla <deepak.sa@samsung.com> --- HTML parser works according to the states. It allows/disallows characters on the basis of the states(Tag name state, End tag open state etc.). It does not take into consideration of validity of that name, and IMHO it should not. HTML parser only coverts them into tokens. Validity has to be checked later. So the HTML parser name validation should not be changed. So the options remains to change the createElement()'s name production. Latest edition of createElement()'s (http://www.w3.org/TR/dom/#dom-document-createelement) name production points to 5th edition XML 1.0 (http://www.w3.org/TR/xml/#NT-Name ). Related to Custom Element: Latest editor's draft of custom element name (http://w3c.github.io/webcomponents/spec/custom/#dfn-custom-element) points to 4th edition NCName : http://www.w3.org/TR/1999/REC-xml-names-19990114/#NT-NCName Shouldn't we change it to 5th edition NCName: http://www.w3.org/TR/xml-names/#NT-NCName ? -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Thursday, 20 November 2014 10:09:22 UTC