<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - Consider making document-level touchstart/touchmove listeners passive by default"
href="https://bugs.webkit.org/show_bug.cgi?id=164016">164016</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Consider making document-level touchstart/touchmove listeners passive by default
</td>
</tr>
<tr>
<th>Classification</th>
<td>Unclassified
</td>
</tr>
<tr>
<th>Product</th>
<td>WebKit
</td>
</tr>
<tr>
<th>Version</th>
<td>WebKit Nightly Build
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Unspecified
</td>
</tr>
<tr>
<th>OS</th>
<td>Unspecified
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>Normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>P2
</td>
</tr>
<tr>
<th>Component</th>
<td>HTML Events
</td>
</tr>
<tr>
<th>Assignee</th>
<td>webkit-unassigned@lists.webkit.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>rbyers@chromium.org
</td>
</tr></table>
<p>
<div>
<pre>Chrome is planning on shipping a breaking change (<a href="https://github.com/WICG/interventions/issues/35">https://github.com/WICG/interventions/issues/35</a>) 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?</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>