Closed
Bug 1574223
Opened 5 years ago
Closed 5 years ago
Consider treating document level ontouchmove as passive
Categories
(Core :: DOM: Events, enhancement)
Core
DOM: Events
Tracking
()
Tracking | Status | |
---|---|---|
firefox70 | --- | fixed |
People
(Reporter: ksenia, Assigned: smaug)
References
()
Details
(Keywords: site-compat)
Attachments
(2 files)
the site is using:
document.ontouchmove = function (e) {
e.preventDefault();
}
which breaks scrolling in Firefox on Android. Looks like Chrome threats ontouchmove here as passive, so preventDefault
doesn't work.
Should we consider doing that as well?
(looks like it was implemented for touchstart and touchmove here https://bugzilla.mozilla.org/show_bug.cgi?id=1449268)
Attached a reduced test case as well
Reporter | ||
Updated•5 years ago
|
Webcompat Priority: --- → ?
Updated•5 years ago
|
Keywords: site-compat
Assignee | ||
Comment 1•5 years ago
•
|
||
touchmove should be considered passive by default.
https://searchfox.org/mozilla-central/source/dom/events/EventListenerManager.cpp#662-663,667-668
Hmm, I wonder if APZ is doing something unexpected here.
And on Windows with touchscreen panning works just fine.
Assignee | ||
Comment 3•5 years ago
|
||
Assignee | ||
Comment 4•5 years ago
|
||
Updated•5 years ago
|
Summary: Consider threatening document level ontouchmove as passive → Consider treating document level ontouchmove as passive
Pushed by opettay@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/e5549942df83
make touchstart/move passive by default also when using event handlers, not only event listeners, r=masayuki
Comment 6•5 years ago
|
||
bugherder |
Status: NEW → RESOLVED
Closed: 5 years ago
status-firefox70:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla70
Comment 7•5 years ago
|
||
Posted site compatibility note: https://www.fxsitecompat.dev/en-CA/docs/2019/ontouchstart-ontouchmove-event-handlers-are-now-passive-by-default/
You need to log in
before you can comment on or make changes to this bug.
Description
•