Add two more hooks to detect target frames.
Each action in the Captured Sites Automation Framework has a target frame. The framework uses the IFrameWaiter object to acquire a handle to the RenderFrameHost of the target frame. A target iframe can be identified by its name, its URL or the origin of its URL. Currently the IFrameWaiter object scans for potential targets everytime Chrome adds a new frame. This change adds 2 additional hooks to IFrameWaiter to scan for potential targets: 1. When a frame changes its name. 2. When a frame finishes loading a new URL. Bug: 847905 Change-Id: Ie2b8c2f19a9f08696d474aff6af019ae116b513c Reviewed-on: https://chromium-review.googlesource.com/c/1260510 Commit-Queue: Yiming Zhou <uwyiming@google.com> Reviewed-by:Sebastien Seguin-Gagnon <sebsg@chromium.org> Cr-Commit-Position: refs/heads/master@{#596888}
Showing
Please register or sign in to comment