Changeset 181552 in webkit
- Timestamp:
- Mar 16, 2015, 5:30:43 AM (11 years ago)
- Location:
- releases/WebKitGTK/webkit-2.8/Source/WebCore
- Files:
-
- 2 edited
-
ChangeLog (modified) (1 diff)
-
rendering/RenderLayerCompositor.cpp (modified) (1 diff)
Legend:
- Unmodified
- Added
- Removed
-
releases/WebKitGTK/webkit-2.8/Source/WebCore/ChangeLog
r181551 r181552 1 2015-03-15 Simon Fraser <simon.fraser@apple.com> 2 3 Remove a redundant repaint when a layer becomes composited 4 https://bugs.webkit.org/show_bug.cgi?id=142711 5 6 Reviewed by Anders Carlsson. 7 8 RenderLayerCompositor::computeCompositingRequirements() doesn't need to call 9 repaintOnCompositingChange() when a layer is going to become composited, 10 because updateBacking() does exactly the same thing. I used an assertion 11 and ran the tests to ensure this wasn't a behavior change. 12 13 * rendering/RenderLayerCompositor.cpp: 14 (WebCore::RenderLayerCompositor::computeCompositingRequirements): 15 1 16 2015-03-14 Adenilson Cavalcanti <cavalcantii@gmail.com> 2 17 -
releases/WebKitGTK/webkit-2.8/Source/WebCore/rendering/RenderLayerCompositor.cpp
r179771 r181552 1412 1412 } 1413 1413 1414 // If the layer is going into compositing mode, repaint its old location.1415 1414 ASSERT(willBeComposited == needsToBeComposited(layer)); 1416 if (!layer.isComposited() && willBeComposited)1417 repaintOnCompositingChange(layer);1418 1415 1419 1416 // Update backing now, so that we can use isComposited() reliably during tree traversal in rebuildCompositingLayerTree().
Note:
See TracChangeset
for help on using the changeset viewer.