Remove hasContentsLayer and isMainFrameRenderViewLayer from CLM

This patch removes some deadcode from CompositedLayerMapping:
1) hasContentsLayer - this function name was confusing.
2) isMainFrameRenderViewLayer - state is now all within CLM.

No new tests, no change in behavior.

Review URL: https://codereview.chromium.org/542863007

git-svn-id: svn://svn.chromium.org/blink/trunk@181526 bbb929c8-8fbe-4397-9dbb-9b2b20218538

third_party/WebKit/Source/core/rendering/compositing/CompositedLayerMapping.h

@@ -90,7 +90,6 @@ public:
     bool hasAncestorClippingLayer() const { return m_ancestorClippingLayer; }
     GraphicsLayer* ancestorClippingLayer() const { return m_ancestorClippingLayer.get(); }
 
-    bool hasContentsLayer() const { return m_foregroundLayer; }
     GraphicsLayer* foregroundLayer() const { return m_foregroundLayer.get(); }
 
     GraphicsLayer* backgroundLayer() const { return m_backgroundLayer.get(); }
@@ -273,8 +272,6 @@ private:
     // Return the opacity value that this layer should use for compositing.
     float compositingOpacity(float rendererOpacity) const;
 
-    bool isMainFrameRenderViewLayer() const;
-
     bool paintsChildren() const;
 
     // Returns true if this layer has content that needs to be rendered by painting into the backing store.