Remove WebGraphicsContext/WebGraphicsContextImpl

third_party/WebKit/Source/web/InspectorOverlay.cpp

Index: third_party/WebKit/Source/web/InspectorOverlay.cpp
diff --git a/third_party/WebKit/Source/web/InspectorOverlay.cpp b/third_party/WebKit/Source/web/InspectorOverlay.cpp
index 5914390d4bf2d41418cefecdc1c1173e55d755d4..d73cd21fa22b40b7bc0d4d96dae0a5a1a60421ba 100644
--- a/third_party/WebKit/Source/web/InspectorOverlay.cpp
+++ b/third_party/WebKit/Source/web/InspectorOverlay.cpp
@@ -51,10 +51,10 @@
 #include "platform/ScriptForbiddenScope.h"
 #include "platform/graphics/GraphicsContext.h"
 #include "platform/graphics/paint/CullRect.h"
+#include "platform/graphics/paint/DisplayItemCacheSkipper.h"
 #include "public/platform/Platform.h"
 #include "public/platform/WebData.h"
 #include "web/PageOverlay.h"
-#include "web/WebGraphicsContextImpl.h"
 #include "web/WebInputEventConversion.h"
 #include "web/WebLocalFrameImpl.h"
 #include "web/WebViewImpl.h"
@@ -109,12 +109,13 @@ public:
         PageOverlay::Delegate::trace(visitor);
     }
 
-    void paintPageOverlay(WebGraphicsContext* context, const WebSize& webViewSize) const override
+    void paintPageOverlay(const PageOverlay&, GraphicsContext& graphicsContext, const WebSize& webViewSize) const override
     {
         if (m_overlay->isEmpty())
             return;
 
-        GraphicsContext& graphicsContext = toWebGraphicsContextImpl(context)->graphicsContext();
+        // Skip cache because the following paint may conflict with the view's real painting.
+        DisplayItemCacheSkipper cacheSkipper(graphicsContext);

[chrishtr, 2016/05/05 16:10:43]

I'm encountering this again in the context of investigation into issue 592915.
This is the only
place other than BoxPainter (for painting theme content) that this is used, so
I'm looking into
getting rid of both.

Why is this necessary again? Why would the PaintController for this overlay be
shared with the
main page?

[Xianzhu, 2016/05/05 16:27:52]

The comment seems a bit misleading. The real reason of cache skipper here is
that we never invalidate display items in this paint controller when the display
items are invalidated, so we must assume that all display items are invalid.
Another choice (which seems more correct) is to clear the paint controller
before painting in PageOverlay::paintContents().

[chrishtr, 2016/05/05 16:30:07]

But where does this PaintController come from? Isn't it new'ed up on every paint
in these cases?

[Xianzhu, 2016/05/05 16:47:33]

Read more code and I found I misunderstood InspectorOverlay. I thought it
painted the inspected frame in some way, but actually it paints
InspectorOverlayPage.html, so this won't conflict with the inspected frame, and
the cache skipper should not be needed.

[chrishtr, 2016/05/05 16:53:04]

Ok I'll put up a patch to remove this then.

         FrameView* view = m_overlay->overlayMainFrame()->view();
         ASSERT(!view->needsLayout());
         view->paint(&graphicsContext, CullRect(IntRect(0, 0, view->width(), view->height())));