Move text-transform to be generated in ComputedStyleBase

third_party/WebKit/Source/core/style/ComputedStyleConstants.h

Index: third_party/WebKit/Source/core/style/ComputedStyleConstants.h
diff --git a/third_party/WebKit/Source/core/style/ComputedStyleConstants.h b/third_party/WebKit/Source/core/style/ComputedStyleConstants.h
index 6873013d46f09286b218226f78d244a1c80bc261..d8c5c62c7a522874054a64d4a00eb32a6f51a9c4 100644
--- a/third_party/WebKit/Source/core/style/ComputedStyleConstants.h
+++ b/third_party/WebKit/Source/core/style/ComputedStyleConstants.h
@@ -355,8 +355,6 @@ enum class ETextAlign : unsigned {
   End,
 };
 
-enum class ETextTransform : unsigned { Capitalize, Uppercase, Lowercase, None };

[napper, 2016/11/28 04:24:45]

Any reason why "None" is not at 0? E.g. 

{ None, Capitalize, Uppercase, Lowercase };

Note they have been defined previously as
"keywords=[none|capitalize|uppercase|lowercase]"

[sashab, 2016/11/30 00:41:38]

It's a good question - that's because the ordering doesn't matter and my program
currently sets the first keyword to the default value :) Since the default value
is none it needs to be at index 0.

I could implement default=none, which I will probably have to do eventually, but
trying to avoid it for as long as possible... 8-)

[alancutter (OOO until 2018), 2016/11/30 03:42:40]

I would call it initial instead of default to be closer to CSS terminology.

Using the first value as the initial value is a bit too magical IMO. I had to go
searching build files to find python scripts and ninja templates to work out
what the initial value will be with this patch. I don't think requiring
initial=none adds too much complexity for the gain in readability.

-
 static const size_t TextDecorationBits = 4;
 enum TextDecoration {
   TextDecorationNone = 0x0,