Don't send touchcancel on touch scroll start

content/browser/renderer_host/input/touch_event_queue.h

Index: content/browser/renderer_host/input/touch_event_queue.h
diff --git a/content/browser/renderer_host/input/touch_event_queue.h b/content/browser/renderer_host/input/touch_event_queue.h
index a0fca696915e0d8ee8590711aa10ceecc0e6f5a2..6b9249e5a0ef101a451a73c0b998a3aefa9ed066 100644
--- a/content/browser/renderer_host/input/touch_event_queue.h
+++ b/content/browser/renderer_host/input/touch_event_queue.h
@@ -38,8 +38,8 @@ class CONTENT_EXPORT TouchEventQueueClient {
 class CONTENT_EXPORT TouchEventQueue {
  public:
   // Different ways of dealing with touch events during scrolling.
-  // TODO(rbyers): Remove (or otherwise update) this once results of
-  // experiments are complete.  http://crbug.com/328503
+  // TODO(rbyers): Remove this once we're confident that touch move absorption
+  // is OK. http://crbug.com/350430
   enum TouchScrollingMode {
     // Send a touchcancel on scroll start and no further touch events for the
     // duration of the scroll.  Chrome Android's traditional behavior.
@@ -51,9 +51,9 @@ class CONTENT_EXPORT TouchEventQueue {
     // Like sync, except that consumed scroll events cause subsequent touchmove
     // events to be suppressed.  Unconsumed scroll events return touchmove
     // events to being dispatched synchronously (so scrolling may be hijacked
-    // when a scroll limit is reached, and later resumed).
+    // when a scroll limit is reached, and later resumed). http://goo.gl/RShsdN
     TOUCH_SCROLLING_MODE_ABSORB_TOUCHMOVE,
-    TOUCH_SCROLLING_MODE_DEFAULT = TOUCH_SCROLLING_MODE_TOUCHCANCEL
+    TOUCH_SCROLLING_MODE_DEFAULT = TOUCH_SCROLLING_MODE_ABSORB_TOUCHMOVE
   };
 
   // The |client| must outlive the TouchEventQueue. If