23781 2013-11-09 02:16:40 +0000 id and class should be case-insensitive in quirks 2014-05-08 06:23:24 +0000 1 1 1 Unclassified WHATWG HTML unspecified PC All RESOLVED FIXED P2 normal Unsorted 1 zcorpan ian annevk bzbarsky ian jackalmage mike Ms2ger www-dom contributor oldest_to_newest 96075 0 zcorpan 2013-11-09 02:16:40 +0000 http://dom.spec.whatwg.org/#concept-id [[ unique identifier (ID) ]] HTML says [[ The unique identifier of HTML elements in documents that are in quirks mode must be treated as ASCII case-insensitive for the purposes of selector matching. Classes from the class attribute of HTML elements in documents that are in quirks mode must be treated as ASCII case-insensitive for the purposes of selector matching. ]] http://www.whatwg.org/specs/web-apps/current-work/multipage/selectors.html#case-sensitivity But this should apply to all elements. It applies to SVG too in browsers and also elements in unknown namespace (in Blink at least, Gecko appears to not support selecting such elements with id selector). Since it applies to all elements it might be good to move to DOM (or be directly in Selectors?). http://software.hixie.ch/utilities/js/live-dom-viewer/saved/2627 (control) http://software.hixie.ch/utilities/js/live-dom-viewer/saved/2628 96076 1 bzbarsky 2013-11-09 02:32:40 +0000 This only applies to CSS matching, right? For example, getElementById() still does case-sensitive matching I believe. Where to spec this is unclear. Maybe the right place is the quirks mode spec, even. 96077 2 annevk 2013-11-09 03:15:56 +0000 So either Selectors fully embraces defining matching in terms of the DOM or it keeps doing its somewhat-DOM-somewhat-abstract dance that's leaky as hell or it makes it fully abstract and then I guess DOM should define DOM-to-abstract. 96078 3 annevk 2013-11-09 03:16:41 +0000 Reassigning to see what Tab thinks. 96091 4 jackalmage 2013-11-10 17:03:39 +0000 Since we decided on a previous issue to keep CSS quirks in the quirks mode spec, I guess we should do the same for this, too. 96094 5 annevk 2013-11-11 01:05:55 +0000 Why did you decide that? The quirks mode specification should disappear. 96125 6 zcorpan 2013-11-11 14:22:14 +0000 Selectors isn't CSS, ba-dum-tsh 104938 7 ian 2014-05-01 22:01:49 +0000 So is the HTML spec wrong here? Or? (This bug isn't assigned to me right now; please do reassign it to me if I should be fixing HTML.) 104948 8 annevk 2014-05-02 07:53:55 +0000 I think this is a bug in Selectors, unless we really want to override Selectors from Quirks Mode, which seems weird and hard to figure out when implementing, but okay. 104963 9 zcorpan 2014-05-02 11:52:57 +0000 I've specified it in quirks mode for now. http://quirks.spec.whatwg.org/#the-case-insensitive-class-and-id-selectors-quirk Hixie, you can drop the part quoted in comment 0 from HTML. 104964 10 zcorpan 2014-05-02 11:56:06 +0000 (But also fix the "everything else" paragraph and maybe point to the quirks spec) 104982 11 ian 2014-05-02 18:22:18 +0000 Why is it better to have it in quirks than in HTML? Aren't we trying to drive the quirks spec to empty and move everything into other specs? 104984 12 Ms2ger 2014-05-02 18:31:45 +0000 On the DOM side, yes. Our friends in the CSSWG don't seem inclined that way, though. 104992 13 ian 2014-05-02 20:42:42 +0000 I'm happy to take care of the CSS stuff that only affects HTML. Does this affect more than HTML? ("Quirks mode" is only possible in text/html, right?) 105019 14 annevk 2014-05-04 08:45:31 +0000 You can have SVG nodes in HTML and it affects them. Or you can have a document that's in quirks mode and pour nodes in it from another document. We made quirks mode a DOM affair, it seems weird for selector matching of DOM to be an HTML affair. 105107 15 ian 2014-05-05 22:00:58 +0000 Shouldn't it be in DOM then? My concern is that the quirks spec is essentially an "errata" spec and that most people won't read it. We need this kind of thing to be immediately visible to implementors. 105109 16 ian 2014-05-05 22:01:18 +0000 (it really _should_ just be in the selectors spec, of course) 105181 17 annevk 2014-05-06 13:26:15 +0000 http://krijnhoetmer.nl/irc-logs/whatwg/20140506#l-5 105314 18 jackalmage 2014-05-07 17:16:55 +0000 (In reply to Anne from comment #17) > http://krijnhoetmer.nl/irc-logs/whatwg/20140506#l-5 It's in Selectors now: http://dev.w3.org/csswg/selectors/#data-model (look at the end of the section) 105317 19 ian 2014-05-07 17:49:33 +0000 Cool. (Probably needs a reference to define "quirks mode", BTW, lest people wonder if "limited quirks" mode counts as "quirks mode" here.) zcorpan, is this all resolved now? 105318 20 contributor 2014-05-07 17:49:58 +0000 Checked in as WHATWG revision r8610. Check-in comment: The quirky class/id selector matching case logic moved to selectors http://html5.org/tools/web-apps-tracker?from=8609&to=8610 105395 21 zcorpan 2014-05-08 06:23:24 +0000 Yep. Thanks! https://github.com/whatwg/quirks/commit/cfda1c1f6d689072118b8e6a9a023f268d3c76be