175869 2017-08-22 19:53:53 -0700 Fallout from making touch events on document/window passive by default 2018-02-26 16:38:27 -0800 1 1 1 Unclassified WebKit UI Events WebKit Nightly Build Unspecified Unspecified RESOLVED CONFIGURATION CHANGED https://bugs.webkit.org/show_bug.cgi?id=175346 https://bugs.webkit.org/show_bug.cgi?id=133112 InRadar P2 Normal --- 1 dino webkit-unassigned ap dave+webkit john.firebaugh jonlee rbyers webkit-bug-importer oldest_to_newest 1341426 0 dino 2017-08-22 19:53:53 -0700 Bug 175346 changed event listeners for touchstart and touchmove on the document (+ body + window + document element) to be passive unless otherwise specified. This bug is going to collect any breakage from that change. When Chrome made this change they saw a small number of sites break. Usually this appears as double scrolling, or some element moving at a different rate from the rest of the page. Please note the URL here, and do not revert the original change. We plan to deal with this through evangelism if we can't detect in code. 1341427 1 webkit-bug-importer 2017-08-22 19:54:25 -0700 <rdar://problem/34027632> 1342379 2 rbyers 2017-08-25 07:23:48 -0700 Note that our guidance to affected sites is to rely on CSS touch-action instead of depending on TouchEvent.preventDefault: https://developers.google.com/web/updates/2017/01/scrolling-intervention Really passive touch listeners are only a reasonable choice when touch-action is fully supported - see https://bugs.webkit.org/show_bug.cgi?id=133112#c2. Safari is likely to see more web compat problems than Chrome unless/until WebKit gets touch-action support. 1400927 3 jonlee 2018-02-20 15:36:46 -0800 We haven't seen reports of this. 1402224 4 john.firebaugh 2018-02-26 16:38:27 -0800 https://bugs.webkit.org/show_bug.cgi?id=182521 https://github.com/mapbox/mapbox-gl-js/issues/6095 > Safari is likely to see more web compat problems than Chrome unless/until WebKit gets touch-action support. +1