Closed
Bug 1212020
Opened 9 years ago
Closed 9 years ago
[e10s] window.scrollX / scrollY values are "lagging" with APZ enabled
Categories
(Core :: Panning and Zooming, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 1209970
Tracking | Status | |
---|---|---|
e10s | - | --- |
People
(Reporter: zer0, Unassigned)
Details
Not sure a better way to formulate that; you can try this test page I made:
https://dl.dropboxusercontent.com/u/5374957/highlighters/apz-test.html
Basically, scripts that rely on `scrollX` / `pageXOffset` and/or `scrollY` / `pageYOffset` to move / draw stuff, are terrible lagging behind the actual scroll. You can see the difference with APZ disabled.
This also affect our devtools – you can try to inspect an element and then scroll, you'll see the inspector's box lag behind with APZ enabled; or you can enable the rulers and scroll the page.
Reporter | ||
Updated•9 years ago
|
Blocks: all-aboard-apz
Reporter | ||
Updated•9 years ago
|
Summary: window.scrollX / scrollY values are "lagging" with APZ enabled → [e10s] window.scrollX / scrollY values are "lagging" with APZ enabled
Comment 1•9 years ago
|
||
Eliminating the lag completely is a non-goal. We want the compositor to be able to respond to scrolls immediately, and content will always be one frame behind, or more if it blows its budget.
I agree that the current lag is terrible. I filed bug 1209970 about reducing it and making it uniform.
I don't have a good solution for the inspector highlighter. I hope getting the lag down to one frame will make it bearable.
Updated•9 years ago
|
tracking-e10s:
--- → -
Comment 2•9 years ago
|
||
I'm going to dupe this to bug 1209970 since we don't have any plans on doing anything else with this.
No longer blocks: all-aboard-apz
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•