Summary: | Fallout from making touch events on document/window passive by default | ||
---|---|---|---|
Product: | WebKit | Reporter: | Dean Jackson <dino> |
Component: | UI Events | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED CONFIGURATION CHANGED | ||
Severity: | Normal | CC: | ap, dave+webkit, john.firebaugh, jonlee, rbyers, webkit-bug-importer |
Priority: | P2 | Keywords: | InRadar |
Version: | WebKit Nightly Build | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
See Also: |
https://bugs.webkit.org/show_bug.cgi?id=175346 https://bugs.webkit.org/show_bug.cgi?id=133112 |
Description
Dean Jackson
2017-08-22 19:53:53 PDT
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. We haven't seen reports of this. 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 |