Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(993)

Unified Diff: Source/core/rendering/RenderBox.cpp

Issue 271803002: [RAL] Fix nested non-composited RenderView repainting (Closed) Base URL: svn://svn.chromium.org/blink/trunk
Patch Set: Proposed fix Created 6 years, 7 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: Source/core/rendering/RenderBox.cpp
diff --git a/Source/core/rendering/RenderBox.cpp b/Source/core/rendering/RenderBox.cpp
index 728025e47a39d2c27a2bbd96138be15a2b6af153..c4e6d0060fd07af4d23176b38addd48ca564c6bb 100644
--- a/Source/core/rendering/RenderBox.cpp
+++ b/Source/core/rendering/RenderBox.cpp
@@ -1588,7 +1588,7 @@ void RenderBox::repaintTreeAfterLayout(const RenderLayerModelObject& repaintCont
// If we are set to do a full repaint that means the RenderView will be
// invalidated. We can then skip issuing of invalidations for the child
// renderers as they'll be covered by the RenderView.
- if (view()->doingFullRepaint() && this != view()) {
+ if (view()->doingFullRepaint()) {
LayoutStateMaintainer statePusher(*this, isTableRow() ? LayoutSize() : locationOffset());
Julien - ping for review 2014/05/30 02:39:32 It is weird that we push LayoutState if we don't e
leviw_travelin_and_unemployed 2014/05/30 15:52:57 We still need to generate our cached repaint rects
RenderObject::repaintTreeAfterLayout(newRepaintContainer);
return;

Powered by Google App Engine
This is Rietveld 408576698