164016 2016-10-26 08:21:25 -0700 Making document-level touchstart/touchmove listeners passive by default 2019-02-06 09:18:27 -0800 1 1 1 Unclassified WebKit DOM WebKit Nightly Build Unspecified Unspecified RESOLVED DUPLICATE 175346 P2 Normal --- 1 rbyers webkit-unassigned bdakin dave+webkit dino sam simon.fraser oldest_to_newest 1244794 0 rbyers 2016-10-26 08:21:25 -0700 Chrome is planning on shipping a breaking change (https://github.com/WICG/interventions/issues/35) to make document-level (window,document,body) touchstart and touchmove listeners passive by default. We've seen huge scroll performance improvements (~40% overall reduction in 99th percentile scroll start time) and relatively little breakage from this. If we can succeed in moving most remaining websites to adopt touch-action (a very simple fix) and therefore show that such a change is entirely web compatible, is this change something the WebKit project would consider? Or is there any reason (other than web compat concerns) why it would be a bad idea for WebKit? 1340776 1 dino 2017-08-21 15:01:55 -0700 Forward duping to https://bugs.webkit.org/show_bug.cgi?id=175346 (because it has more content) *** This bug has been marked as a duplicate of bug 175346 *** 1503169 2 lforschler 2019-02-06 09:18:27 -0800 Mass move bugs into the DOM component.