Refactor matched rule ranges.

Refactor matched rule ranges.

For matched CSS rules we need to know where the UA rules end and the
author rules begin. This CL simplifies this by having a single index for
the last UA rule. -1 means there are no UA rules, otherwise it's the
index of the last UA rule in the array. Convenience methods are added to
return the first/last rule indices for UA and author rules.

The rule ranges used to be updated for every added rule. Now, just update
the last UA rule index when sorting and transferring UA rules. That means
we don't have to pass the ranges as parameters anymore.

R=timloh@chromium.org,esprehn@chromium.org

Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=196036

[Timothy Loh, 2015-05-28 00:18:39]

lgtm

Can we (in a separate patch) make the ranges use begin/end instead of
first/last? This will remove the need for a special -1 value.

[rune, 2015-05-28 06:27:57]

The CQ bit was checked by rune@opera.com

[commit-bot: I haz the power, 2015-05-28 06:28:14]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1155393002/1

[commit-bot: I haz the power, 2015-05-28 06:31:52]

Committed patchset #1 (id:1) as
https://src.chromium.org/viewvc/blink?view=rev&revision=196036

[rune, 2015-05-28 09:58:45]

On 2015/05/28 00:18:39, Timothy Loh wrote:
> lgtm
> 
> Can we (in a separate patch) make the ranges use begin/end instead of
> first/last? This will remove the need for a special -1 value.

https://codereview.chromium.org/1162583002/

[esprehn, 2015-06-02 03:19:36]

https://codereview.chromium.org/1155393002/diff/1/Source/core/css/ElementRule...
File Source/core/css/ElementRuleCollector.h (right):

https://codereview.chromium.org/1155393002/diff/1/Source/core/css/ElementRule...
Source/core/css/ElementRuleCollector.h:121: const MatchResult& matchedResult();
matchResult() const; ?