From ffa12fa4c6a57059fb969c6f3f34ff8c331cc427 Mon Sep 17 00:00:00 2001
From: Markus Stange <mstange@themasta.com>
Date: Fri, 9 Aug 2019 00:47:05 +0000
Subject: [PATCH] Bug 1571862 - When the layer change region is too complex,
 always set mInvalidRegion to mRenderBounds, even if we're currently rendering
 to mTarget. r=mattwoodrow

We only use the result of this calculation for composites to the actual window
(and stash it for later if this composite is to an external target), so
mTargetBounds is always unrelated.

Differential Revision: https://phabricator.services.mozilla.com/D40871

--HG--
extra : moz-landing-system : lando
---
 gfx/layers/composite/LayerManagerComposite.cpp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gfx/layers/composite/LayerManagerComposite.cpp b/gfx/layers/composite/LayerManagerComposite.cpp
index e7120f2ea311..9a7d85d820c4 100644
--- a/gfx/layers/composite/LayerManagerComposite.cpp
+++ b/gfx/layers/composite/LayerManagerComposite.cpp
@@ -564,7 +564,7 @@ void LayerManagerComposite::UpdateAndRender() {
         mRoot, changed, nullptr);
 
     if (overflowed) {
-      changed = mTarget ? mTargetBounds : mRenderBounds;
+      changed = mRenderBounds;
     }
 
     mInvalidRegion.Or(mInvalidRegion, changed);