CSS: Additional asserts for style invalidation

third_party/WebKit/Source/core/css/RuleFeature.h

Index: third_party/WebKit/Source/core/css/RuleFeature.h
diff --git a/third_party/WebKit/Source/core/css/RuleFeature.h b/third_party/WebKit/Source/core/css/RuleFeature.h
index eb4637caf1878c4c32596feaed361e8e828c8262..0f1f3163bb43790ef6a614845ce08e174aa40769 100644
--- a/third_party/WebKit/Source/core/css/RuleFeature.h
+++ b/third_party/WebKit/Source/core/css/RuleFeature.h
@@ -123,7 +123,7 @@ private:
     // Each map entry is either a DescendantInvalidationSet or SiblingInvalidationSet.
     // When both are needed, we store the SiblingInvalidationSet, and use it to hold the DescendantInvalidationSet.
     using InvalidationSetMap = HashMap<AtomicString, RefPtr<InvalidationSet>>;
-    using PseudoTypeInvalidationSetMap = HashMap<CSSSelector::PseudoType, RefPtr<InvalidationSet>, WTF::IntHash<unsigned>, WTF::UnsignedWithZeroKeyHashTraits<unsigned>>;
+    using PseudoTypeInvalidationSetMap = HashMap<int, RefPtr<InvalidationSet>>; // key values are CSSSelector::PseudoType

[esprehn, 2016/09/01 05:30:22]

Does this need changing in this patch?

[Eric Willigers, 2016/09/01 14:56:31]

No, we can focus on non-zero keys in this patch.

 
     struct FeatureMetadata {
         DISALLOW_NEW();