Move Document global rule data to CSSGlobalRuleSet.

Move Document global rule data to CSSGlobalRuleSet.

This CL is split out from [1] with some modifications.

Instead of storing these data in the StyleResolver, create a new class
to store them in StyleEngine instead. See the design document linked
from issue 401359 which talks about moving this content off of
StyleResolver. Also made a note that we should further try to contain
as much of this data as possible per TreeScope to avoid the need for
constantly having to update these meta data for shadow tree
modifications.

We get rid of some of the duplicate storing of some of these features.
See what was previously set on StyleEngine (resetCSSFeatureFlags()).

This is also in preparation for async stylesheet update (issue 567021).
There are few places where we synchronously update this new rule set
directly after marking it as dirty which will happen later when all
parts of [1] lands.

Another synchronous update we will be able to remove later is making
the RuleFeatureSet up-to-date when scheduling style invalidations
(marked as TODOs for sync calls to ensureResolver()). The need for
these calls is supported by the added invalidation tests which would
otherwise fail.

[1] https://codereview.chromium.org/1913833002/

BUG=401359, 567021
Committed: https://crrev.com/17bc158897bb9b9d6b1400ed76092a412de16bc9
Cr-Commit-Position: refs/heads/master@{#428327}

[rune, 2016-10-26 13:37:02]

The CQ bit was checked by rune@opera.com to run a CQ dry run

[commit-bot: I haz the power, 2016-10-26 13:37:12]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[rune, 2016-10-26 15:02:14]

Ptal

[commit-bot: I haz the power, 2016-10-26 17:33:00]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-10-26 17:33:01]

Dry run: This issue passed the CQ dry run.

[rune, 2016-10-26 17:40:06]

rune@opera.com changed reviewers:
+ esprehn@chromium.org, meade@chromium.org

[meade_UTC10, 2016-10-28 01:54:02]

lgtm

Nice CL! \o/

[rune, 2016-10-28 07:00:15]

The CQ bit was checked by rune@opera.com

[commit-bot: I haz the power, 2016-10-28 07:00:26]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-10-28 07:02:35]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-10-28 07:02:36]

Try jobs failed on following builders:
  linux_chromium_asan_rel_ng on master.tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)

[rune, 2016-10-28 08:56:07]

The CQ bit was checked by rune@opera.com

[rune, 2016-10-28 08:56:07]

The patchset sent to the CQ was uploaded after l-g-t-m from meade@chromium.org
Link to the patchset: https://codereview.chromium.org/2451893003/#ps20001
(title: "Rebased.")

[commit-bot: I haz the power, 2016-10-28 08:56:19]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-10-28 10:20:54]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2016-10-28 10:22:24]

Description was changed from

==========
Move Document global rule data to CSSGlobalRuleSet.

This CL is split out from [1] with some modifications.

Instead of storing these data in the StyleResolver, create a new class
to store them in StyleEngine instead. See the design document linked
from issue 401359 which talks about moving this content off of
StyleResolver. Also made a note that we should further try to contain
as much of this data as possible per TreeScope to avoid the need for
constantly having to update these meta data for shadow tree
modifications.

We get rid of some of the duplicate storing of some of these features.
See what was previously set on StyleEngine (resetCSSFeatureFlags()).

This is also in preparation for async stylesheet update (issue 567021).
There are few places where we synchronously update this new rule set
directly after marking it as dirty which will happen later when all
parts of [1] lands.

Another synchronous update we will be able to remove later is making
the RuleFeatureSet up-to-date when scheduling style invalidations
(marked as TODOs for sync calls to ensureResolver()). The need for
these calls is supported by the added invalidation tests which would
otherwise fail.

[1] https://codereview.chromium.org/1913833002/

BUG=401359,567021
==========

to

==========
Move Document global rule data to CSSGlobalRuleSet.

This CL is split out from [1] with some modifications.

Instead of storing these data in the StyleResolver, create a new class
to store them in StyleEngine instead. See the design document linked
from issue 401359 which talks about moving this content off of
StyleResolver. Also made a note that we should further try to contain
as much of this data as possible per TreeScope to avoid the need for
constantly having to update these meta data for shadow tree
modifications.

We get rid of some of the duplicate storing of some of these features.
See what was previously set on StyleEngine (resetCSSFeatureFlags()).

This is also in preparation for async stylesheet update (issue 567021).
There are few places where we synchronously update this new rule set
directly after marking it as dirty which will happen later when all
parts of [1] lands.

Another synchronous update we will be able to remove later is making
the RuleFeatureSet up-to-date when scheduling style invalidations
(marked as TODOs for sync calls to ensureResolver()). The need for
these calls is supported by the added invalidation tests which would
otherwise fail.

[1] https://codereview.chromium.org/1913833002/

BUG=401359,567021

Committed: https://crrev.com/17bc158897bb9b9d6b1400ed76092a412de16bc9
Cr-Commit-Position: refs/heads/master@{#428327}
==========

[commit-bot: I haz the power, 2016-10-28 10:22:25]

Patchset 2 (id:??) landed as
https://crrev.com/17bc158897bb9b9d6b1400ed76092a412de16bc9
Cr-Commit-Position: refs/heads/master@{#428327}