Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(204)

Unified Diff: Source/core/css/CSSSelector.h

Issue 772103002: Collect content:attr(...)-features in RuleFeatureSet. (Closed) Base URL: https://chromium.googlesource.com/chromium/blink.git@master
Patch Set: Avoid findPropertyIndex when possible. Created 6 years ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: Source/core/css/CSSSelector.h
diff --git a/Source/core/css/CSSSelector.h b/Source/core/css/CSSSelector.h
index c9c67144cfc29adae054124bc0578068893c11b9..e971707e6a34be5f71b9b4f054e8f4751d21609d 100644
--- a/Source/core/css/CSSSelector.h
+++ b/Source/core/css/CSSSelector.h
@@ -50,7 +50,7 @@ namespace blink {
//
// The order of tagHistory() varies depending on the situation.
// * Relations using combinators (http://www.w3.org/TR/css3-selectors/#combinators), such as descendant, sibling, etc., are parsed
- // right-to-left (in the example above, this is why .c is earlier in the tagHistory() chain than .a.b).
+ // right-to-left (in the example above, this is why #c is earlier in the tagHistory() chain than .a.b).
// * SubSelector relations are parsed left-to-right in most cases (such as the .a.b example above); a counter-example is the
// ::content pseudo-element. Most (all?) other pseudo elements and pseudo classes are parsed left-to-right.
// * ShadowPseudo relations are parsed right-to-left. Example: summary::-webkit-details-marker is parsed as:
« no previous file with comments | « LayoutTests/fast/css/invalidation/content-attr-style-mutation-expected.html ('k') | Source/core/css/RuleFeature.h » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698