Handle pointer-events: none in browser process hittesting.

content/renderer/render_frame_proxy.cc

Index: content/renderer/render_frame_proxy.cc
diff --git a/content/renderer/render_frame_proxy.cc b/content/renderer/render_frame_proxy.cc
index a44bb34e16df13f22837d12585e8f3e266bedbe7..9e4b014f4cdd3e17055ce95a06697286e9d9cd02 100644
--- a/content/renderer/render_frame_proxy.cc
+++ b/content/renderer/render_frame_proxy.cc
@@ -194,6 +194,18 @@ bool RenderFrameProxy::IsMainFrameDetachedFromTree() const {
       render_view_->webview()->mainFrame()->isWebLocalFrame();
 }
 
+void RenderFrameProxy::WillBeginCompositorFrame() {
+  if (ChildFrameCompositingHelper* compositing_helper =
+          compositing_helper_.get()) {
+    FrameHostMsg_HittestData_Params params;
+    params.surface_id = compositing_helper->surface_id();
+    params.ignored_for_hittest = web_frame_->ignoredForHittest();
+    render_widget_->QueueMessage(
+        new FrameHostMsg_HittestData(render_widget_->routing_id(), params),
+        MESSAGE_DELIVERY_POLICY_WITH_NEXT_SWAP);

[piman, 2016/01/16 01:25:36]

You want MESSAGE_DELIVERY_POLICY_WITH_VISUAL_STATE to synchronize with the
commit.
MESSAGE_DELIVERY_POLICY_WITH_NEXT_SWAP skips the commit logic.

[lfg, 2016/01/18 21:35:20]

Done. It doesn't matter here since they are replaced, but wouldn't that cause
multiple updates to a single surface be submitted on a frame?

[piman, 2016/01/20 01:21:19]

I'm not fully sure I understand the question...

With MESSAGE_DELIVERY_POLICY_WITH_VISUAL_STATE it will send the message exactly
once - either with the commit, or, if there is no pending commit or the commit
or swap gets cancelled (e.g. no update), as a regular message.
With MESSAGE_DELIVERY_POLICY_WITH_NEXT_SWAP it would send the message exactly
once too, but it would skip the commit flow, i.e. if there's already a frame
pending before the commit, the message may be sent earlier (but "too early" in
your case).

WillBeginCompositorFrame should be called exactly once per RFP per commit, so I
don't think you're sending redundant information per commit (though one could
argue that you could send a message only if web_frame_->ignoredForHittest()
changes, not sure if it matters).

+  }
+}
+
 void RenderFrameProxy::DidCommitCompositorFrame() {
   if (compositing_helper_.get())
     compositing_helper_->DidCommitCompositorFrame();