3 Get rid of "non-composited contents" in CoordinatedLayerTreeHost
4 https://bugs.webkit.org/show_bug.cgi?id=110355
5
6 Reviewed by NOBODY (OOPS!).
7
8 When in force compositing mode, always assume that the main layer needs
9 a backing store. Make setVisibleContentRectTrajectoryVector and accumulatedCoverRect
10 recursive so that they don't rely on a specialized layer.
11
12 No new testable behavior, changes to coverRect and trajectory vector only
13 affect tiling latency in rare cases that are not trivial to test.
14
15 * platform/graphics/texmap/coordinated/CoordinatedGraphicsLayer.cpp:
16 (WebCore::CoordinatedGraphicsLayer:setVisibleContentRectTrajectoryVector):
17 Make the trajectory vector recursive, though limited only to layers with
18 translate/identity. This allows us to keep the trajectory vector while removing
19 the non-composited contents specialization.
20
21 (WebCore::CoordinatedGraphicsLayer::accumulatedCoverRect):
22 Added accumulatedCoverRect, so that the coverRect calculations for the UI process
23 are not bound to the non-composited contents layer.
24
25 (WebCore::CoordinatedGraphicsLayer::findDescendantWithContentsRecursively):
26 Instead of saving a reference to the non-composited contents layer, we assume that
27 the first layer we found recursively which has contents is the one to be used for
28 coverRect/trajectory calculations.
29
30 (WebCore):
31 * platform/graphics/texmap/coordinated/CoordinatedGraphicsLayer.h:
32 (CoordinatedGraphicsLayer):
33 * rendering/RenderLayerBacking.cpp:
34 (WebCore::RenderLayerBacking::paintsIntoWindow):
35 Always create a layer for the non-composited contents when in forceCompositing mode.
36
372013-04-26 Noam Rosenthal <noam@webkit.org>
38