- From: <bugzilla@jessica.w3.org>
- Date: Wed, 01 May 2013 05:47:01 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21889 Bug ID: 21889 Summary: [Custom]: Consider making all names/types lowercase Classification: Unclassified Product: WebAppsWG Version: unspecified Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P2 Component: Component Model Assignee: dglazkov@chromium.org Reporter: dominicc@chromium.org QA Contact: public-webapps-bugzilla@w3.org Blocks: 14968 The HTML spec is littered with "localName ... converted to ASCII lowercase". Is the same required for the Custom Elements spec? Converting custom tags to lowercase will simplify implementations, because HTML documents already convert tags to lowercase. Type extensions could be handled in a case-sensitive way, since attribute values are case-preserving, but it seems more consistent to convert them to lowercase too. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Wednesday, 1 May 2013 05:47:04 UTC