[css-ui] Add support for caret-color property

third_party/WebKit/Source/core/css/resolver/StyleBuilderCustom.cpp

Index: third_party/WebKit/Source/core/css/resolver/StyleBuilderCustom.cpp
diff --git a/third_party/WebKit/Source/core/css/resolver/StyleBuilderCustom.cpp b/third_party/WebKit/Source/core/css/resolver/StyleBuilderCustom.cpp
index a32acd73177428e1ecc8af92d6a37da71502e5db..c1243b2c973b198bd66e8298de96b7fe5be0222c 100644
--- a/third_party/WebKit/Source/core/css/resolver/StyleBuilderCustom.cpp
+++ b/third_party/WebKit/Source/core/css/resolver/StyleBuilderCustom.cpp
@@ -92,6 +92,7 @@ static inline bool isValidVisitedLinkProperty(CSSPropertyID id) {
     case CSSPropertyBorderRightColor:
     case CSSPropertyBorderTopColor:
     case CSSPropertyBorderBottomColor:
+    case CSSPropertyCaretColor:

[Timothy Loh, 2016/11/22 02:17:35]

Do we need to do this? What are the use cases for styling caret-color
differently for visited and unvisited links? I think it'd be better to not
consider caret-color specially for :visited. Otherwise we'd need to add tests
for this behaviour.

[Manuel Rego, 2016/11/22 09:36:01]

We actually have a test for this specific behavior:
  editing/caret/caret-color-015.html

The tests were validated by Florian Rivoal (the spec editor)
so I believe we really want to support this.

Authors usually modify the color of the link if it's visited,
if the link is editable it'd be nice to have a different caret-color too.

     case CSSPropertyColor:
     case CSSPropertyFill:
     case CSSPropertyOutlineColor: