Currently, InteractiveDetector will consider the first pointer down as the input delay if it encounters a pointer up. This does not work fine in the case that we have an onpointerdown event handler and we touch scroll the page, because in this case there is a pointerDown, pointerCausedUaAction, and pointerUp. In addition, pointerDown plus pointerCancel plus pointerUp is also a scroll. Thus, these pointerDown cases need to be excluded.

It should be noted that not all scrolls that go through the renderer will exhibit this pattern. In fact, without the onpointerdown handler, the touch scroll will be given to InteractiveDetector as gestures that are correctly excluded as inputs.