23742 2013-11-06 16:24:00 +0000 Element tag name matching should not be fully case insensitive 2013-11-08 21:05:28 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#case-sensitivity P3 normal Unsorted 1 contributor ian bzbarsky ian mike contributor oldest_to_newest 95872 0 contributor 2013-11-06 16:24:00 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/selectors.html Multipage: http://www.whatwg.org/C#case-sensitivity Complete: http://www.whatwg.org/c#case-sensitivity Referrer: http://www.whatwg.org/specs/web-apps/current-work/multipage/ Comment: Element tag name matching should not be fully case insensitive Posted from: 173.48.23.63 by bzbarsky@mit.edu User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:28.0) Gecko/20100101 Firefox/28.0 95873 1 bzbarsky 2013-11-06 16:30:26 +0000 I thought we had reached consensus that what we want is for HTML elements in HTML documents to compare the ascii-lowercased selector to the localName of the element and for others to just compare to the localName, both compares being case-sensitive. That way you can use interned strings in selector matching for better performance. But the spec text doesn't seem to reflect that. A testcase is at http://software.hixie.ch/utilities/js/live-dom-viewer/?saved=2623 and shows green text in Blink, Gecko, and Presto. It shows red in Trident, but Trident has an incorrect localName ("div" instead of "DIV") in this case. 95880 2 ian 2013-11-06 19:36:44 +0000 I don't recall such a decision, but it seems reasonable, if somewhat unintuitive. Done for element names (see checkin below). It looks like the same applies to attribute names; should I do that too? http://software.hixie.ch/utilities/js/live-dom-viewer/?saved=2623 95881 3 ian 2013-11-06 19:37:06 +0000 Oops, wrong link, sorry: http://software.hixie.ch/utilities/js/live-dom-viewer/?saved=2624 95884 4 bzbarsky 2013-11-06 19:52:58 +0000 Yeah, I think attribute names should work similarly. 95885 5 bzbarsky 2013-11-06 19:53:09 +0000 And thank you! 95995 6 ian 2013-11-07 22:40:24 +0000 Ok, the attribute selector equivalent text is a bit convoluted, so don't hesitate to reopen the bug if I screwed it up some how. 95996 7 contributor 2013-11-07 22:42:02 +0000 Checked in as WHATWG revision r8261. Check-in comment: Match reality better in terms of selector case-sensitivity for attributes as well http://html5.org/tools/web-apps-tracker?from=8260&to=8261 96040 8 bzbarsky 2013-11-08 21:05:28 +0000 seems reasonable at first glance.