24005 2013-12-05 15:08:35 +0000 Attribute values can't always be matched case-sensitively 2015-09-01 13:20:01 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED MOVED http://www.whatwg.org/specs/web-apps/current-work/#case-sensitivity P3 normal Unsorted 1 contributor ian annevk bzbarsky fs ian jackalmage mike zcorpan contributor oldest_to_newest 97172 0 contributor 2013-12-05 15:08:35 +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: Attribute values can't always be matched case-sensitively 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 97174 1 bzbarsky 2013-12-05 15:10:50 +0000 Consider this simple testcase: <!DOCTYPE html> <style> input[type="radio"] { outline: 20px solid green; } </style> <input type="RADIO"> <script> document.write(document.querySelector("input").getAttribute("type")); </script> This shows the green outline in every UA I've tried (Presto, Blink, WebKit, Gecko, recent Trident). But per spec the selector should not match, since the spec required case-sensitive matching of attribute values... I will argue the spec is what should change here. 97176 2 bzbarsky 2013-12-05 15:15:15 +0000 *** Bug 24004 has been marked as a duplicate of this bug. *** 97191 3 ian 2013-12-05 18:20:34 +0000 zcorpan requested that we drop this in bug 13757. 97203 4 bzbarsky 2013-12-05 19:02:14 +0000 Is any UA planning to actually implement zcorpan's proposed change? 97327 5 annevk 2013-12-09 14:50:14 +0000 Would it not be much better not have a magic list of attributes in our matching code? We did discuss this with dbaron and others at the time. 97329 6 bzbarsky 2013-12-09 14:55:16 +0000 Maybe. Please show me a UA that's willing to change to what the spec currently says. 97330 7 bzbarsky 2013-12-09 14:58:10 +0000 And implement it in all modes, to boot. Unless we want to have a quirk for this. 97331 8 annevk 2013-12-09 15:01:24 +0000 I did not intend for this to be a quirk. 97346 9 zcorpan 2013-12-09 19:22:07 +0000 I've filed https://code.google.com/p/chromium/issues/detail?id=327060 98538 10 ian 2014-01-15 22:57:55 +0000 I guess the question is, how long should we wait before we give up and resurrect the old spec text here? 103643 11 ian 2014-04-09 22:15:19 +0000 Looks like we'll have data on this momentarily now. 104533 12 zcorpan 2014-04-28 08:37:20 +0000 Unfortunately the use counter turned out to be triggered by the user agent stylesheet. Fix on the way; give it some more time. 107395 13 ian 2014-06-05 19:58:56 +0000 Any idea what the ETA is for the use counter to update to reporting the new data? 107641 14 zcorpan 2014-06-11 09:10:49 +0000 It seems the fix got stuck in review and the developer got swamped by other things. fs will carry on with it though, so probably the fix will land soonish and then we'll have to wait for the new use counter data. 110724 15 ian 2014-08-28 18:48:11 +0000 fs: any news here? 110763 16 zcorpan 2014-08-29 11:51:46 +0000 The fix https://codereview.chromium.org/417353004 landed 2014-08-01 The use counter is http://www.chromestatus.com/metrics/feature/timeline/popularity/244 but we need to wait and see what it's like when the fix has been in stable for a few weeks. 111753 17 ian 2014-09-18 17:25:43 +0000 Looks like the fix either didn't do a complete job of fixing it, or there's more of this out there than we realised. I would have thought that exluding UA style sheets would have brought this down dramatically. 111806 18 zcorpan 2014-09-19 15:22:20 +0000 No, it hasn't reached stable yet. It should be in 38. 111811 19 ian 2014-09-19 17:25:18 +0000 Oh, ok. What happened in August then? Is that just the drop from dev users? 111908 20 fs 2014-09-22 09:18:07 +0000 (In reply to Ian 'Hixie' Hickson from comment #19) > Oh, ok. What happened in August then? Is that just the drop from dev users? Yes. 111932 21 ian 2014-09-22 16:52:37 +0000 Oh wow, ok. That's a huge drop already then. Looking forward to the data! 116343 22 zcorpan 2014-12-15 12:45:17 +0000 It seems it's around 0.1% now. Probably this is too high for it to be worth it. 116580 23 ian 2014-12-19 22:57:38 +0000 So we should resurrect the old text? 116781 24 zcorpan 2015-01-05 09:51:00 +0000 Yes. 116852 25 ian 2015-01-06 22:46:30 +0000 Revert https://html5.org/r/6695 122973 26 annevk 2015-09-01 13:20:01 +0000 https://github.com/whatwg/html/pull/74