This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
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
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.
*** Bug 24004 has been marked as a duplicate of this bug. ***
zcorpan requested that we drop this in bug 13757.
Is any UA planning to actually implement zcorpan's proposed change?
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.
Maybe. Please show me a UA that's willing to change to what the spec currently says.
And implement it in all modes, to boot. Unless we want to have a quirk for this.
I did not intend for this to be a quirk.
I've filed https://code.google.com/p/chromium/issues/detail?id=327060
I guess the question is, how long should we wait before we give up and resurrect the old spec text here?
Looks like we'll have data on this momentarily now.
Unfortunately the use counter turned out to be triggered by the user agent stylesheet. Fix on the way; give it some more time.
Any idea what the ETA is for the use counter to update to reporting the new data?
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.
fs: any news here?
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.
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.
No, it hasn't reached stable yet. It should be in 38.
Oh, ok. What happened in August then? Is that just the drop from dev users?
(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.
Oh wow, ok. That's a huge drop already then. Looking forward to the data!
It seems it's around 0.1% now. Probably this is too high for it to be worth it.
So we should resurrect the old text?
Yes.
Revert https://html5.org/r/6695
https://github.com/whatwg/html/pull/74