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

third_party/WebKit/Source/core/css/CSSPropertyEquality.cpp

Index: third_party/WebKit/Source/core/css/CSSPropertyEquality.cpp
diff --git a/third_party/WebKit/Source/core/css/CSSPropertyEquality.cpp b/third_party/WebKit/Source/core/css/CSSPropertyEquality.cpp
index 1ab54cd0d103898397946039e58a8788a004835d..be8e6f2822b03ae77a137b3b391171e98a6d5c87 100644
--- a/third_party/WebKit/Source/core/css/CSSPropertyEquality.cpp
+++ b/third_party/WebKit/Source/core/css/CSSPropertyEquality.cpp
@@ -116,6 +116,9 @@ bool CSSPropertyEquality::propertiesEqual(CSSPropertyID prop,
       return a.bottom() == b.bottom();
     case CSSPropertyBoxShadow:
       return dataEquivalent(a.boxShadow(), b.boxShadow());
+    case CSSPropertyCaretColor:
+      return a.caretColor() == b.caretColor() &&
+             a.visitedLinkCaretColor() == b.visitedLinkCaretColor();

[yosin_UTC9, 2016/11/22 02:25:10]

Why do we need to handle "visited link caret color" specially? Is it for
"currentColor"?
It seems this is copying logic of "color". But, it seems doing so in two places
is redundant.

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

It's not only color, all the other color properties have a similar logic:
CSSPropertyBackgroundColor, CSSPropertyBorderXXXColor,
CSSPropertyColumnRuleColor, CSSPropertyWebkitTextStrokeColor.

     case CSSPropertyClip:
       return a.clip() == b.clip();
     case CSSPropertyColor: