Always use the WebFrameWidget when attaching the root graphics
layer or the compositor animation timeline in ChromeClientImpl.
Now that we always instantiate a WebFrameWidget for local
roots, we can remove the fallback code that goes directly
through WebView.
This change also fixes an issue where local roots were not
being passed to
ChromeClientImpl::attachCompositorAnimationTimeline which
caused the AnimationTimeline to be attached to the wrong
widget.
BUG=587025
Review-Url: https://codereview.chromium.org/2036403002
Cr-Commit-Position: refs/heads/master@{#403781}
diff --git a/content/renderer/render_frame_impl.h b/content/renderer/render_frame_impl.h
index f3d5f6f9e..2ff0dd7 100644
--- a/content/renderer/render_frame_impl.h
+++ b/content/renderer/render_frame_impl.h
@@ -464,7 +464,7 @@
blink::WebSandboxFlags sandbox_flags,
const blink::WebFrameOwnerProperties& frame_owner_properties) override;
void didChangeOpener(blink::WebFrame* frame) override;
- void frameDetached(blink::WebFrame* frame, DetachType type) override;
+ void frameDetached(blink::WebLocalFrame* frame, DetachType type) override;
void frameFocused() override;
void willClose(blink::WebFrame* frame) override;
void didChangeName(const blink::WebString& name,
