Use explicit case-insensitive attribute-value matching in UA-stylesheets

Use explicit case-insensitive attribute-value matching in UA-stylesheets

With the "i" (case-insensitive) matching modifier introduced in
https://codereview.chromium.org/330043003/, it becomes possible to
refine the hits on the CaseInsensitiveAttrSelectorMatch use-counter
by applying the modifier to all rules in the UA-stylesheets which
perform an attribute-value match on one of the attributes that - due
to legacy reasons - should be matched case-insensitively.

Most of the modified rules involve the 'type' attribute on <input>
elements, but there are a few others as well ('dir' and 'align').

The goal of this is to be able to get rid of the legacy-induced case-
insensitive cases and leave the "i" flag as a mechanism to opt-in to
case-insensitive matching. See https://crbug.com/327060 for further info.

BUG=327060, 366563
Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=179401

[fs, 2014-08-01 13:41:42]

This is a mechanical change. The intention is to get a better idea of how common
the case-insensitive "fallback" (legacy behavior) code-path is. Previously the
use-counter was "disturbed" by the UA-styles, and with the added 'i' modifier
and this we hope to get a more accurate reading. PTAL.

[Mike West, 2014-08-01 14:04:35]

LGTM.

I see you added it to the BUG line, but can you add an explicit note in the CL
description pointing to
https://code.google.com/p/chromium/issues/detail?id=327060 as the end goal? It
wasn't initially clear to me what that UseCounter was good for.

Thanks!

-mike

[fs, 2014-08-01 14:29:04]

On 2014/08/01 14:04:35, Mike West wrote:
> LGTM.
> 
> I see you added it to the BUG line, but can you add an explicit note in the CL
> description pointing to
> https://code.google.com/p/chromium/issues/detail?id=327060 as the end goal? It
> wasn't initially clear to me what that UseCounter was good for.

Done.

[fs, 2014-08-01 14:29:28]

The CQ bit was checked by fs@opera.com

[commit-bot: I haz the power, 2014-08-01 14:29:58]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/fs@opera.com/417353004/1

[commit-bot: I haz the power, 2014-08-01 14:35:18]

Change committed as 179401

[eseidel, 2014-08-01 16:35:43]

I'm confused by what the goal is here?  We can also disable UseCounters while
parsing UA sheets.  I think we already do...

[philipj_slow, 2014-08-02 04:56:23]

Selector matching happens after parsing, I guess that's why.