add pan-x and pan-y support to CSS touch-action parsing.

Source/core/css/resolver/StyleBuilderCustom.cpp

Index: Source/core/css/resolver/StyleBuilderCustom.cpp
diff --git a/Source/core/css/resolver/StyleBuilderCustom.cpp b/Source/core/css/resolver/StyleBuilderCustom.cpp
old mode 100644
new mode 100755
index 28be921bf49737901e596f61f7b7ff8ffe66d1d4..087baa7ad8d0129bc99fc18d9c78a77ca7d16b01
--- a/Source/core/css/resolver/StyleBuilderCustom.cpp
+++ b/Source/core/css/resolver/StyleBuilderCustom.cpp
@@ -564,6 +564,16 @@ void StyleBuilderFunctions::applyValueCSSPropertyVerticalAlign(StyleResolverStat
     state.style()->setVerticalAlignLength(primitiveValue->convertToLength<FixedConversion | PercentConversion>(state.cssToLengthConversionData()));
 }
 
+void StyleBuilderFunctions::applyValueCSSPropertyTouchAction(StyleResolverState& state, CSSValue* value)
+{
+    TouchAction action = RenderStyle::initialTouchAction();
+    for (CSSValueListIterator i(value); i.hasMore(); i.advance()) {
+        CSSValue* item = i.value();
+        action |= *toCSSPrimitiveValue(item);

[Rick Byers, 2013/12/10 21:57:14]

The other indication that this should be calling your touch-action conversion
routines directly is that we should make it clear here that only the
touch-action values are permitted (eg. what would it mean if there was a length
value or something here?).  Hopefully this falls out cleanly from the removal of
the value conversion functions.

+    }
+    state.style()->setTouchAction(action);
+}
+
 static void resetEffectiveZoom(StyleResolverState& state)
 {
     // Reset the zoom in effect. This allows the setZoom method to accurately compute a new zoom in effect.