Closed
Bug 1819848
Opened 2 years ago
Closed 2 years ago
Additional hardening of the compositor thumb size calculation
Categories
(Core :: Panning and Zooming, task, P2)
Core
Panning and Zooming
Tracking
()
RESOLVED
FIXED
112 Branch
Tracking | Status | |
---|---|---|
firefox112 | --- | fixed |
People
(Reporter: botond, Assigned: botond)
References
Details
Attachments
(3 files)
Spinning out the initial fix idea for bug 1818702 from bug 1818702 comment 14, which is really a hardening against other possible minor mismatches between the main-thread and compositor calculations, into this bug.
Assignee | ||
Comment 1•2 years ago
|
||
In principle, the calculated scale should be 1.0 if we are not async-zoomed,
but sometimes things like rounding error can cause the scale to be slightly
off.
Assignee | ||
Comment 2•2 years ago
|
||
Depends on D171437
Assignee | ||
Comment 3•2 years ago
|
||
Depends on D171438
Pushed by bballo@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/3e1124bfbcbd
Only scale the thumb in the compositor if we are async-zoomed. r=rzvncj
https://hg.mozilla.org/integration/autoland/rev/367f1d038bea
If we don't scale the thumb, use the unscaled length in the position calculation. r=rzvncj
https://hg.mozilla.org/integration/autoland/rev/222a3e2f0f2e
Move calculations that are only needed for the 'if (haveAsyncZoom)' branch into that branch. r=rzvncj
Comment 5•2 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/3e1124bfbcbd
https://hg.mozilla.org/mozilla-central/rev/367f1d038bea
https://hg.mozilla.org/mozilla-central/rev/222a3e2f0f2e
Status: NEW → RESOLVED
Closed: 2 years ago
status-firefox112:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 112 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•