Bug 282750. Don't worry about over-complex opaque regions when we want to add a rect that will cover the entire region (and thus simplify it). r+sr=bzbarsky
git-svn-id: svn://10.0.0.236/trunk@181714 18797224-902f-48f8-a5cc-f745e15eee43
This commit is contained in:
parent
522e71126c
commit
f347fe6bd8
@ -4002,8 +4002,10 @@ void nsViewManager::OptimizeDisplayList(const nsVoidArray* aDisplayList, const n
|
||||
} else {
|
||||
element->mBounds = tmpRgn.GetBounds();
|
||||
|
||||
PRBool tooComplex = aOpaqueRegion.GetNumRects() > MAX_OPAQUE_REGION_COMPLEXITY &&
|
||||
!element->mBounds.Contains(aOpaqueRegion.GetBounds());
|
||||
// See whether we should add this view's bounds to aOpaqueRegion
|
||||
if (aOpaqueRegion.GetNumRects() <= MAX_OPAQUE_REGION_COMPLEXITY &&
|
||||
if (!tooComplex &&
|
||||
// a view is opaque if it is neither transparent nor transluscent
|
||||
(!(element->mFlags & (VIEW_TRANSPARENT | VIEW_TRANSLUCENT))
|
||||
// also, treat it as opaque if it's drawn onto a uniform background
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user