Optionally skip rendering a snapshotted picture
Categories
(Core :: Graphics: WebRender, task, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox135 | --- | fixed |
People
(Reporter: nical, Assigned: nical)
References
Details
(Whiteboard: [viewtransitions:m1:gfx])
Attachments
(1 file)
For the live capture of the new-state, the view-transition spec requires that the capture be rendered "as if it was an image". The plan is to use an actual Image display item for it.
To render the live snapshot as an image in the same frame it is captured (since it is live), we have to prevent the capturing step from actually drawing into the parent so that only the image item will. Conveniently, the spec also wants the live capture to be snatched into the front layer so this should help.
Note: I bet that we will eventually come to regret the resulting API. It's really odd and surprising to have something at an arbitrary place in the display list that is rendered but not composited, so that something elsewhere in the display list can render it. The better long term solution would be to extract these stacking contexts from the flow of the DL by either making them separate pipelines or explicitly having multiple roots in the DL/frame (internally that's what webrender will probably have to do to manage the snapshots).
However the way this weird API seems to perfectly sit in between the quirks of how the spec and and display list building want to operate.
Updated•1 year ago
|
| Assignee | ||
Comment 1•1 year ago
|
||
A dettached stacking context is cached into a snapshot image but not drawn into the frame.
Updated•1 year ago
|
Updated•1 year ago
|
Description
•