Bug 164016
| Summary: | Making document-level touchstart/touchmove listeners passive by default | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Rick Byers <rbyers> |
| Component: | DOM | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | Normal | CC: | bdakin, dave+webkit, dino, sam, simon.fraser |
| Priority: | P2 | ||
| Version: | WebKit Nightly Build | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
Rick Byers
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?
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Dean Jackson
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 ***
Lucas Forschler
Mass move bugs into the DOM component.