Layers that have a backdrop-filter should paints contents

third_party/WebKit/Source/core/style/ComputedStyle.h

Index: third_party/WebKit/Source/core/style/ComputedStyle.h
diff --git a/third_party/WebKit/Source/core/style/ComputedStyle.h b/third_party/WebKit/Source/core/style/ComputedStyle.h
index 26f7320010e555eb7f9e02b38971f02276784a07..268febfdfc42389eea5a155541ddbbff646aa092 100644
--- a/third_party/WebKit/Source/core/style/ComputedStyle.h
+++ b/third_party/WebKit/Source/core/style/ComputedStyle.h
@@ -417,6 +417,7 @@ public:
     bool hasMarginAfterQuirk() const { return marginAfter().quirk(); }
 
     bool hasBackgroundImage() const { return m_background->background().hasImage(); }
+    bool hasBackgroundImageOrBackdropFilter() const { return hasBackgroundImage() || hasBackdropFilter(); }
     bool hasFixedBackgroundImage() const { return m_background->background().hasFixedImage(); }
 
     bool hasEntirelyFixedBackground() const;
@@ -437,7 +438,7 @@ public:
         Color color = visitedDependentColor(CSSPropertyBackgroundColor);
         if (color.alpha())
             return true;
-        return hasBackgroundImage();
+        return hasBackgroundImageOrBackdropFilter();

[pdr., 2016/01/27 05:52:09]

Is this tested? This was my concern in the previous review.

I looked at some callsites of style->hasBackground() and I'm not sure this is
correct. Just as an example, LayoutBoxModelObject::backgroundStolenForBeingBody
has a hasBackground call... is it correct to return false if there's a backdrop
filter?

Renaming this to be hasBackgroundOrBackdropFilter might help as well, but I'm
primarily worried about the edge-case bugs this introduces.

[jaydasika, 2016/01/27 23:59:42]

Ah, I see your point. I think we should have a separate hasBackdropFilter,
because we can't have it in hasBackground(for the reasons you mentioned) and not
in hasBoxDecorations (for reasons mentioned in the previous review). WDYT ?     

     }
 
     LayoutRectOutsets imageOutsets(const NinePieceImage&) const;