Don't paint effectively-invisible layers with tiny opacity in SPv2. |
||
Issue descriptionNoted while working on http://crrev.com/2523103003. Believe we should consider kMinimumVisibleOpacity in PaintLayerPainter::PaintedOutputInvisible for SPv2 as we do for SPv1. Likely need to make sure we do still paint them if there's an animation.
,
Apr 28 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/caaa5c77ce09501d9dd409bde61ae226e1768b7f commit caaa5c77ce09501d9dd409bde61ae226e1768b7f Author: wkorman <wkorman@chromium.org> Date: Fri Apr 28 20:49:34 2017 Skip paint chunks with effectively invisible opacity. For SPv2 we always paint effectively invisible content, but during layerization we scrutinize effect node and skip chunks that would be effectively invisible. This simplifies code in SPv2 while still avoiding the resource and processing overhead of creating, managing and rastering a layer for that chunk. BUG= 713403 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.linux:linux_layout_tests_slimming_paint_v2 Review-Url: https://codereview.chromium.org/2833883003 Cr-Commit-Position: refs/heads/master@{#468120} [modify] https://crrev.com/caaa5c77ce09501d9dd409bde61ae226e1768b7f/third_party/WebKit/Source/core/paint/PaintLayerPainter.cpp [modify] https://crrev.com/caaa5c77ce09501d9dd409bde61ae226e1768b7f/third_party/WebKit/Source/core/paint/PaintLayerPainterTest.cpp [modify] https://crrev.com/caaa5c77ce09501d9dd409bde61ae226e1768b7f/third_party/WebKit/Source/platform/graphics/compositing/PaintArtifactCompositor.cpp [modify] https://crrev.com/caaa5c77ce09501d9dd409bde61ae226e1768b7f/third_party/WebKit/Source/platform/graphics/compositing/PaintArtifactCompositorTest.cpp
,
Apr 28 2017
|
||
►
Sign in to add a comment |
||
Comment 1 by schenney@chromium.org
, Apr 20 2017