Deprecate 'intrinsic' and 'min-intrinsic' CSS keywords, attempt 2

Source/core/frame/UseCounter.cpp

Index: Source/core/frame/UseCounter.cpp
diff --git a/Source/core/frame/UseCounter.cpp b/Source/core/frame/UseCounter.cpp
index 898a167e9aaf25add85b58b512786c78200a79a7..186beab82c550d37b33d1f98fefcccaa392e3ce8 100644
--- a/Source/core/frame/UseCounter.cpp
+++ b/Source/core/frame/UseCounter.cpp
@@ -945,6 +945,12 @@ String UseCounter::deprecationMessage(Feature feature)
     case HeaderValueNotMatchingRFC7230:
         return "Header values not matching to RFC 7230, will be deprecated (see: https://www.chromestatus.com/feature/6457425448140800).";
 
+    case LegacyCSSValueIntrinsic:
+        return "The 'intrinsic' CSS keyword is deprecated and will be removed in M48, around January 2015. Use the standard 'max-content' keyword instead.";
+
+    case LegacyCSSValueMinIntrinsic:

[esprehn, 2015/09/19 01:25:56]

Where does this case get handled? I only see the LegacyCSSValueIntrinsic enum
value used in StyleAdjuster.

+        return "The 'min-intrinsic' CSS keyword is deprecated and will be removed in M48, around January 2015. Use the standard 'min-content' keyword instead.";
+
     // Features that aren't deprecated don't have a deprecation message.
     default:
         return String();