Fix bug Emulation.setVirtualTimePolicy and waitForNavigation
If only a single call to Emulation.setVirtualTimePolicy is made with waitForNavigation:true then addInspectorEmulationAgent wasn't getting called in time, which meant InspectorEmulationAgent::FrameStartedLoading wasn't called for the navigation, which meant the virtual time policy was never changing. Bug: 777763 Change-Id: I7525ed1de924319c195ecfdd602c3fad808eba59 Reviewed-on: https://chromium-review.googlesource.com/918665Reviewed-by:Dmitry Gozman <dgozman@chromium.org> Commit-Queue: Alex Clarke <alexclarke@chromium.org> Cr-Commit-Position: refs/heads/master@{#536721}
Showing
Please register or sign in to comment