Note that this should include skipping the touch-action computation (Edge doesn't do it either during a fling - see issue 631899). Perhaps we can safely ignore the explicit passive:false regions too.
In addition to better repeated fling performance, this should also generally be a better UX. When you're repeatedly flinging a scroller, you don't expect it to suddently stop moving if you happen to do one of the flings overtop of an element that cancels the touch or disables the scroll via touch-action.
Cc: dtapu...@chromium.org Summary: Make touch events on a flinging layer non-blocking (including ignoring touch-action) (was: Make touchstart events during fling non-blocking)
Comment 1 by rbyers@chromium.org
, Apr 4 2016