23255 2013-09-16 14:10:00 +0000 [Custom]: Requirements on custom element type names 2013-10-05 11:52:43 +0000 1 1 1 Unclassified WebAppsWG HISTORICAL - Component Model unspecified PC All RESOLVED FIXED P2 normal --- 14968 1 zcorpan dglazkov annevk mrbkap public-webapps-bugzilla oldest_to_newest 93424 0 zcorpan 2013-09-16 14:10:00 +0000 "The custom element type identifies a custom element interface and is a sequence of alphanumeric ASCII characters" HTML's data-* attributes aren't restricted to alphanumeric ASCII. Why is the alphenumeric requirement there? Does it make sense for data-* also? Or vice versa? Another thing is that the names should be required to be in ASCII lowercase, since the HTML parser case-folds. 94318 1 dglazkov 2013-10-04 19:21:46 +0000 I should just remove the "alpanumeric ASCII characters" bit. The NCName product is clearly specified just a few words later, and it's sufficient. As far as the case is concerned, case-folding is only applicable in HTML documents. The definition construction algorithm does the actual work: https://dvcs.w3.org/hg/webcomponents/raw-file/tip/spec/custom/index.html#dfn-definition-construction-algorithm 94319 2 dglazkov 2013-10-04 19:28:20 +0000 https://dvcs.w3.org/hg/webcomponents/rev/f790c96a29e3 94330 3 zcorpan 2013-10-04 20:35:16 +0000 I think it's a bad idea to allow uppercase names in XHTML. It violates http://www.w3.org/TR/html-design-principles/#dom-consistency data-* attributes are required to be in lowercase (in the ASCII range). 94331 4 dglazkov 2013-10-04 20:46:13 +0000 (In reply to Simon Pieters from comment #3) > I think it's a bad idea to allow uppercase names in XHTML. It violates > http://www.w3.org/TR/html-design-principles/#dom-consistency > > data-* attributes are required to be in lowercase (in the ASCII range). I don't have super-strong opinions here. If I remember correctly, I was just trying not to impose too many restrictions. Since SVG already has mixed-case names, and custom elements allow extending SVGElement, it seems only fair to let those extending SVG to use mixed case. 94332 5 zcorpan 2013-10-04 20:58:25 +0000 SVG isn't going to introduce any new names with uppercase, since doing so would mean updating the case fixup tables in the HTML parser. 94335 6 dglazkov 2013-10-04 21:09:23 +0000 (In reply to Simon Pieters from comment #5) > SVG isn't going to introduce any new names with uppercase, since doing so > would mean updating the case fixup tables in the HTML parser. Okay, so basically we should presume that all mixed-case names are mistakes of the past and we just force lowercase for all new elements? I am ok with that. Anne, Blake, how does this sound to you? 94348 7 dglazkov 2013-10-04 22:43:24 +0000 https://dvcs.w3.org/hg/webcomponents/rev/4817a2c68123 https://dvcs.w3.org/hg/webcomponents/rev/a6acb7dcfda5 94366 8 annevk 2013-10-05 11:52:43 +0000 ASCII lowercase, yes. Looks good.