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

Source/core/css/CSSComputedStyleDeclaration.cpp

 /*
  * Copyright (C) 2004 Zack Rusin <zack@kde.org>
  * Copyright (C) 2004, 2005, 2006, 2007, 2008, 2009, 2010, 2011, 2012 Apple Inc. All rights reserved.
  * Copyright (C) 2007 Alexey Proskuryakov <ap@webkit.org>
  * Copyright (C) 2007 Nicholas Shanks <webkit@nickshanks.com>
  * Copyright (C) 2011 Sencha, Inc. All rights reserved.
  *
  * This library is free software; you can redistribute it and/or
  * modify it under the terms of the GNU Lesser General Public
  * License as published by the Free Software Foundation; either
@@ skipping 1524 matching lines @@
         return cssValuePool().createIdentifierValue(CSSValueBold);
     case FontWeight800:
         return cssValuePool().createIdentifierValue(CSSValue800);
     case FontWeight900:
         return cssValuePool().createIdentifierValue(CSSValue900);
     }
     ASSERT_NOT_REACHED();
     return cssValuePool().createIdentifierValue(CSSValueNormal);
 }
 
+static PassRefPtr<CSSValue> touchActionFlagsToCSSValue(int touchAction)

[Rick Byers, 2013/12/06 21:44:04]

This should take a TouchAction.   You could always add an operator& to
TouchAction (along with your operator|) if you like.

[gnana, 2013/12/10 18:24:37]

Done.

+{
+    RefPtr<CSSValueList> list = CSSValueList::createSpaceSeparated();
+    if (touchAction & TouchActionNone)
+        list->append(cssValuePool().createIdentifierValue(CSSValueNone));
+    if (touchAction & TouchActionAuto)
+        list->append(cssValuePool().createIdentifierValue(CSSValueAuto));
+    if (touchAction & TouchActionPanX)

[Rick Byers, 2013/12/06 21:44:04]

We should probably ASSERT or otherwise reject the invalid combinations here (so
we're sure we never produce a value list that would fail to parse) - including
an empty list. 

Is there precedent for similar invalid value handling elsewhere? 

[gnana, 2013/12/10 18:24:37]

I m checking on this. i will update this in next patch.

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

Ok.  Whatever the common error-handling pattern seems to be is fine with me - it
seems like it should be pretty unlikely for this to ever be an issue.

[gnana, 2013/12/11 14:02:53]

Done.

+        list->append(cssValuePool().createIdentifierValue(CSSValuePanX));
+    if (touchAction & TouchActionPanY)
+        list->append(cssValuePool().createIdentifierValue(CSSValuePanY));
+
+    if (!list->length())
+        return cssValuePool().createIdentifierValue(CSSValueAuto);
+    return list.release();
+}
+
 static bool isLayoutDependent(CSSPropertyID propertyID, PassRefPtr<RenderStyle> style, RenderObject* renderer)
 {
     // Some properties only depend on layout in certain conditions which
     // are specified in the main switch statement below. So we can avoid
     // forcing layout in those conditions. The conditions in this switch
     // statement must remain in sync with the conditions in the main switch.
     // FIXME: Some of these cases could be narrowed down or optimized better.
     switch (propertyID) {
     case CSSPropertyBottom:
     case CSSPropertyGridDefinitionColumns:
@@ skipping 754 matching lines @@
             return cssValuePool().createValue(style->textSecurity());
         case CSSPropertyWebkitTextStrokeColor:
             return currentColorOrValidColor(*style, style->textStrokeColor());
         case CSSPropertyWebkitTextStrokeWidth:
             return zoomAdjustedPixelValue(style->textStrokeWidth(), *style);
         case CSSPropertyTextTransform:
             return cssValuePool().createValue(style->textTransform());
         case CSSPropertyTop:
             return valueForPositionOffset(*style, CSSPropertyTop, renderer, m_node->document().renderView());
         case CSSPropertyTouchAction:
-            return cssValuePool().createValue(style->touchAction());
+            return touchActionFlagsToCSSValue(style->touchAction());
         case CSSPropertyTouchActionDelay:
             return cssValuePool().createValue(style->touchActionDelay());
         case CSSPropertyUnicodeBidi:
             return cssValuePool().createValue(style->unicodeBidi());
         case CSSPropertyVerticalAlign:
             switch (style->verticalAlign()) {
                 case BASELINE:
                     return cssValuePool().createIdentifierValue(CSSValueBaseline);
                 case MIDDLE:
                     return cssValuePool().createIdentifierValue(CSSValueMiddle);
@@ skipping 900 matching lines @@
     static const CSSPropertyID propertiesAfterSlashSeperator[3] = { CSSPropertyBackgroundSize, CSSPropertyBackgroundOrigin,
                                                                     CSSPropertyBackgroundClip };
 
     RefPtr<CSSValueList> list = CSSValueList::createSlashSeparated();
     list->append(valuesForShorthandProperty(StylePropertyShorthand(CSSPropertyBackground, propertiesBeforeSlashSeperator, WTF_ARRAY_LENGTH(propertiesBeforeSlashSeperator))));
     list->append(valuesForShorthandProperty(StylePropertyShorthand(CSSPropertyBackground, propertiesAfterSlashSeperator, WTF_ARRAY_LENGTH(propertiesAfterSlashSeperator))));
     return list.release();
 }
 
 } // namespace WebCore