Fuchsia: Always attach WebContentsObserver to a Frame's WebContents.
Currently, a Frame doesn't process WebContentsObserver methods until a FIDL NavigationEventObserver is registered. WebContentsObserver is useful for more than just navigation events, though! In cases where a Frame is created but never passed a N.E.O., observer events like ReadyToCommitNavigation() were not being received, which interfered with on-load script injection. This CL fixes the issue by attaching the observer at Frame creation time. Bug: 903880 Change-Id: Ie3ab194fbaa60a5e18a4150be3ce4c6f7345845f Reviewed-on: https://chromium-review.googlesource.com/c/1328147 Commit-Queue: Kevin Marshall <kmarshall@chromium.org> Reviewed-by:Wez <wez@chromium.org> Reviewed-by:
Sergey Ulanov <sergeyu@chromium.org> Cr-Commit-Position: refs/heads/master@{#606997}
Showing
Please register or sign in to comment