GitLab

When ProactivelySwapBrowsingInstance is turned on with the level set to
CrossSiteReuseProcess (see crrev.com/c/2043521), renderer-initiated
navigations might trigger a BrowsingInstance swap which leads to a
RenderView swap, etc, with a possibility of the current renderer process
getting reused. Some parts of the TestRunner code does not expect this
(they expect the main window RenderView change always go hand-in-hand
with RenderProcess change, and that we always restart with a clean state
after those navigations), so we are updating it.

Bug: 977562
Change-Id: I469d28b2553b1a7d4e8025c30c3a5593267cb42a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2094480
Commit-Queue: Rakina Zata Amni <rakina@chromium.org>
Reviewed-by: Alex Moshchuk <alexmos@chromium.org>
Reviewed-by: Łukasz Anforowicz <lukasza@chromium.org>
Cr-Commit-Position: refs/heads/master@{#751564}