GitLab

The should let us deprecate waitForNavigation parameter to
Emulation.setVirtualTimePolicy and make its contract a bit
more sensible: instead of virtual time being set in advance
and waiting to kick-in after the navigation, we let the
navigation wait for the virtual time budget to be granted
before the document is actually loaded. This removes the
race between document resources loading (and, conditionally,
consuming 10ms each) and the client granting the budget.

Change-Id: Iffc794a450dbb8cb6ae1d37100386f00c7638abf
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2531363Reviewed-by: Dmitry Gozman <dgozman@chromium.org>
Commit-Queue: Andrey Kosyakov <caseq@chromium.org>
Cr-Commit-Position: refs/heads/master@{#826355}