Handle pointer-events: none in browser process hittesting.

content/renderer/render_frame_proxy.cc

 // Copyright 2014 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 #include "content/renderer/render_frame_proxy.h"
 
 #include <stdint.h>
 #include <map>
 #include <utility>
 
@@ skipping 176 matching lines @@
   CHECK(result.second) << "Inserted a duplicate item.";
 }
 
 bool RenderFrameProxy::IsMainFrameDetachedFromTree() const {
   if (SiteIsolationPolicy::IsSwappedOutStateForbidden())
     return false;
   return web_frame_->top() == web_frame_ &&
       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();
 }
 
 void RenderFrameProxy::SetReplicatedState(const FrameReplicationState& state) {
   DCHECK(web_frame_);
   web_frame_->setReplicatedOrigin(state.origin);
   web_frame_->setReplicatedSandboxFlags(state.sandbox_flags);
   web_frame_->setReplicatedName(blink::WebString::fromUTF8(state.name));
@@ skipping 276 matching lines @@
                                     blink::WebLocalFrame* source) {
   int source_routing_id = RenderFrameImpl::FromWebFrame(source)->GetRoutingID();
   Send(new FrameHostMsg_AdvanceFocus(routing_id_, type, source_routing_id));
 }
 
 void RenderFrameProxy::frameFocused() {
   Send(new FrameHostMsg_FrameFocused(routing_id_));
 }
 
 }  // namespace