Closed
Bug 1675888
Opened 5 years ago
Closed 5 years ago
Reduce apz.velocity_relevance_time_ms from 150 to 100
Categories
(Core :: Panning and Zooming, defect)
Core
Panning and Zooming
Tracking
()
RESOLVED
FIXED
84 Branch
| Tracking | Status | |
|---|---|---|
| firefox84 | --- | fixed |
People
(Reporter: mstange, Assigned: mstange)
Details
Attachments
(1 file)
The pref apz.velocity_relevance_time_ms is currently set to 150.
Chrome uses 100 for the equivalent variable.
I think we should match their value. A smaller window size reacts faster to changes in velocity and acceleration, and is less likely to overestimate the velocity during fling gestures. And now that we take historic touch positions into account (since bug 1615858), we should always have enough data points within the 100ms window to compute an accurate velocity.
|
Assignee | |
Comment 1•5 years ago
|
||
Pushed by mstange@themasta.com:
https://hg.mozilla.org/integration/autoland/rev/c9bd1e6cebd9
Reduce apz.velocity_relevance_time_ms from 150 to 100, to match Chrome. r=botond
|
||
Comment 3•5 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
status-firefox84:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 84 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•