Closed
Bug 1242821
Opened 9 years ago
Closed 1 year ago
"Scroll of Lorem Ipsum" demo scrolls poorly
Categories
(Core :: Panning and Zooming, defect, P3)
Tracking
()
People
(Reporter: mattwoodrow, Unassigned)
References
()
Details
(Keywords: perf, Whiteboard: [gfx-noted])
Attachments
(1 file)
60.59 KB,
text/plain
|
Details |
See URL field for testcase.
This scrolls really smoothly on chrome, but is quite delayed on firefox (with APZ).
The demo is using separate copies of the content for each segment in the ends, and updates the positions of all the copies during an rAF callback to match the scroll position of the primary content.
Updated•9 years ago
|
Blocks: apz-desktop
Comment 1•9 years ago
|
||
Nice layer tree :)
Matt, does this layer tree look reasonable to you? If not, we should probably address any Layout issues that give rise to this layer tree first.
Attachment #8712347 -
Flags: feedback?(matt.woodrow)
Reporter | ||
Comment 2•9 years ago
|
||
It's reasonable in the sense that it's what the page is asking for.
The page makes two DOM clones of the scrolled content for each 'segment' of the curled ends. By default there are 20 segments ('num' in the page source).
Reporter | ||
Updated•9 years ago
|
Attachment #8712347 -
Flags: feedback?(matt.woodrow)
Updated•9 years ago
|
Whiteboard: [gfx-noted]
Comment 3•9 years ago
|
||
Not really sure what to do about this one. I guess if we can make painting fast enough it would improve the behavior. I got a profile at https://cleopatra.io/#report=d3e2877c45b1eb0e0f1674ac4095a0baae2dd21a but nothing jumps out at me.
Keywords: perf
Comment 4•9 years ago
|
||
This is a testcase where empty transactions for transform changes should actually help. But unfortunately we're not hitting that path. And the painting in the profile indicates that the transforms are not prerendered.
Updated•9 years ago
|
status-firefox48:
--- → affected
Updated•9 years ago
|
status-firefox49:
--- → affected
Updated•8 years ago
|
status-firefox50:
--- → affected
Updated•8 years ago
|
Updated•8 years ago
|
status-firefox52:
--- → wontfix
status-firefox53:
--- → affected
Updated•2 years ago
|
Severity: normal → S3
Comment 5•1 year ago
|
||
This demo seems to perform well now. Should this bug be closed?
Flags: needinfo?(botond)
Comment 6•1 year ago
|
||
Yes, let's close this. My guess is this was fixed by WebRender.
Status: NEW → RESOLVED
Closed: 1 year ago
Flags: needinfo?(botond)
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•