Implement touch-action pan-x/pan-y handling on the main thread

Source/web/tests/data/touch-action-tests.css

Index: Source/web/tests/data/touch-action-tests.css
diff --git a/Source/web/tests/data/touch-action-tests.css b/Source/web/tests/data/touch-action-tests.css
old mode 100644
new mode 100755
index 386d132c10d12f3592995f651ade9de9e4cbe62a..9763b108f40cdd4fcd8e700342748564894aca90
--- a/Source/web/tests/data/touch-action-tests.css
+++ b/Source/web/tests/data/touch-action-tests.css
@@ -10,6 +10,18 @@
   -ms-touch-action: auto;
   touch-action: auto;
 }
+.ta-panx {
+  -ms-touch-action: pan-x;
+  touch-action: pan-x;
+}
+.ta-pany {
+  -ms-touch-action: pan-y;
+  touch-action: pan-y;
+}
+.ta-panxy {
+  -ms-touch-action: pan-x pan-y;
+  touch-action: pan-x pan-y;
+}
 
 /* Make it easy to visualize div boundaries */
 [expected-action] {
@@ -25,6 +37,15 @@
 [expected-action=auto]::before {
   content: "AUTO \2190 ";
 }
+[expected-action=pan-x]::before {
+  content: "PAN-X \2190 ";
+}
+[expected-action=pan-y]::before {
+  content: "PAN-Y \2190 ";
+}
+[expected-action=pan-x pan-y]::before {

[Rick Byers, 2013/12/12 20:47:24]

Chrome claims this selector syntax is invalid.  Putting "pan-x pan-y" in quotes
seems to fix it.  Alternately it's probably simpler to just invent a token like
'pan-x-y' for this case.

[gnana, 2013/12/13 16:52:53]

Done.

+  content: "PAN-X PAN-Y \2190 ";
+}
 
 body {
   /* Leave gap for test to scroll down */