Non passive touch end or touch cancel listeners should not block scroll.

third_party/WebKit/LayoutTests/fast/events/touch/resources/compositor-touch-hit-rects.js

Index: third_party/WebKit/LayoutTests/fast/events/touch/resources/compositor-touch-hit-rects.js
diff --git a/third_party/WebKit/LayoutTests/fast/events/touch/resources/compositor-touch-hit-rects.js b/third_party/WebKit/LayoutTests/fast/events/touch/resources/compositor-touch-hit-rects.js
index a6c6e27d9f25ae4fc0f9b4dc9c5b922aec46a469..02cfeb7ad1cfc890c28debd714f6c97c4cba7e91 100644
--- a/third_party/WebKit/LayoutTests/fast/events/touch/resources/compositor-touch-hit-rects.js
+++ b/third_party/WebKit/LayoutTests/fast/events/touch/resources/compositor-touch-hit-rects.js
@@ -136,6 +136,12 @@ if (window.internals) {
 window.onload = function() {
     // Run each general test case.
     var tests = document.querySelectorAll('.testcase');
+
+    // Add document wide touchend and touchcancel events to ensure they
+    // are not added to the compositor hit test rects.

[tdresser, 2016/04/13 16:52:35]

Nit: we're adding listeners, not events.

I'm a bit confused by this comment. Why does adding these listeners effect
whether or not we add to the compositor hit test rects?

[dtapuska, 2016/04/13 18:00:15]

touchend and touchcancel use to be added to the hit test rects to block scroll.
So this is a negative test; in that I add the listeners and ensure the test
doesn't fail in adding the entire document to the hit test rects.

[tdresser, 2016/04/13 18:44:39]

Ah, makes sense.

Maybe reword "to ensure" to "and ensure".

[dtapuska, 2016/04/13 18:49:08]

Done.

+    document.documentElement.addEventListener('touchend', listener, false);
+    document.documentElement.addEventListener('touchcancel', listener, false);
+
     for ( var i = 0; i < tests.length; i++) {
         // Force a compositing update before testing each case to ensure that
         // any subsequent touch rect updates are actually done because of