Confirmed users
523
edits
Gecko:Layers: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
|||
| Line 25: | Line 25: | ||
** Roc: assuming that "container" layers are always formed by compositing together their children, what is the point of having backing store for them? For leaf layers, I assume we would keep them in backing store (as long as clients hold references to them, which may only be as long as one paint cycle). My proposal makes no provision for "faulting in" the contents of discarded layers. | ** Roc: assuming that "container" layers are always formed by compositing together their children, what is the point of having backing store for them? For leaf layers, I assume we would keep them in backing store (as long as clients hold references to them, which may only be as long as one paint cycle). My proposal makes no provision for "faulting in" the contents of discarded layers. | ||
** Jeff: My response to that is: what's the point creating layers for things that we don't want a backing store for? | ** Jeff: My response to that is: what's the point creating layers for things that we don't want a backing store for? | ||
== Use case == | |||
Assume we have a webpage with a container containing some web content and a video. This container has a 3d-transform applied to it. What should the layer hierarchy look like? | |||
== Roc == | == Roc == | ||