Fix two tests that started failing with PlzNavigate after browser-initiated navigations stopped goi…

Fix two tests that started failing with PlzNavigate after browser-initiated navigations stopped going to the renderer first if there was no beforeunload handler in r460581.

The bug was that the tests were sending multiple navigations to different tabs in parallel. While a nested message loop was running for one navigation, the notification that about:blank (initial URL) of the tab was firing and causing the login interstitial (for the next navigation) to be removed. This doesn't happen in practice because we don't run nested message loops that dispatch IPCs in production, but we do for browser tests.

This fixes
LoginPromptBrowserTest.SupplyRedundantAuths
LoginPromptBrowserTest.CancelRedundantAuths

BUG=705559
Review-Url: https://codereview.chromium.org/2792493002
Cr-Commit-Position: refs/heads/master@{#461031}
Committed: https://chromium.googlesource.com/chromium/src/+/bc0329821f41940fff03c16dd1e36293d1042218

[jam, 2017-03-31 03:46:58]

jam@chromium.org changed reviewers:
+ nasko@chromium.org

[jam, 2017-03-31 03:52:09]

Description was changed from

==========
Fix two tests that started failing with PlzNavigate after browser-initiated
navigations stopped going to the renderer first if there was no beforeunload
handler.

The bug was that the tests were sending multiple navigations to different tabs
in parallel. While a nested message loop was running for one navigation, the
notification that about:blank (initial URL) of the tab was firing and causing
the login interstitial (for the next navigation) to be removed. This doesn't
happen in practice because we don't run nested message loops that dispatch IPCs
in production, but we do for browser tests.

This fixes
LoginPromptBrowserTest.SupplyRedundantAuths
LoginPromptBrowserTest.CancelRedundantAuths

BUG=705559
==========

to

==========
Fix two tests that started failing with PlzNavigate after browser-initiated
navigations stopped going to the renderer first if there was no beforeunload
handler in r460581.

The bug was that the tests were sending multiple navigations to different tabs
in parallel. While a nested message loop was running for one navigation, the
notification that about:blank (initial URL) of the tab was firing and causing
the login interstitial (for the next navigation) to be removed. This doesn't
happen in practice because we don't run nested message loops that dispatch IPCs
in production, but we do for browser tests.

This fixes
LoginPromptBrowserTest.SupplyRedundantAuths
LoginPromptBrowserTest.CancelRedundantAuths

BUG=705559
==========

[nasko, 2017-03-31 03:53:50]

LGTM

[jam, 2017-03-31 03:54:20]

The CQ bit was checked by jam@chromium.org

[commit-bot: I haz the power, 2017-03-31 03:54:43]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-03-31 04:35:17]

CQ is committing da patch.

Bot data: {"patchset_id": 1, "attempt_start_ts": 1490932460313390, "parent_rev":
"c0da73caa1828ecd87a9e1c443108685a8eca5ce", "commit_rev":
"bc0329821f41940fff03c16dd1e36293d1042218"}

[commit-bot: I haz the power, 2017-03-31 04:35:57]

Description was changed from

==========
Fix two tests that started failing with PlzNavigate after browser-initiated
navigations stopped going to the renderer first if there was no beforeunload
handler in r460581.

The bug was that the tests were sending multiple navigations to different tabs
in parallel. While a nested message loop was running for one navigation, the
notification that about:blank (initial URL) of the tab was firing and causing
the login interstitial (for the next navigation) to be removed. This doesn't
happen in practice because we don't run nested message loops that dispatch IPCs
in production, but we do for browser tests.

This fixes
LoginPromptBrowserTest.SupplyRedundantAuths
LoginPromptBrowserTest.CancelRedundantAuths

BUG=705559
==========

to

==========
Fix two tests that started failing with PlzNavigate after browser-initiated
navigations stopped going to the renderer first if there was no beforeunload
handler in r460581.

The bug was that the tests were sending multiple navigations to different tabs
in parallel. While a nested message loop was running for one navigation, the
notification that about:blank (initial URL) of the tab was firing and causing
the login interstitial (for the next navigation) to be removed. This doesn't
happen in practice because we don't run nested message loops that dispatch IPCs
in production, but we do for browser tests.

This fixes
LoginPromptBrowserTest.SupplyRedundantAuths
LoginPromptBrowserTest.CancelRedundantAuths

BUG=705559

Review-Url: https://codereview.chromium.org/2792493002
Cr-Commit-Position: refs/heads/master@{#461031}
Committed:
https://chromium.googlesource.com/chromium/src/+/bc0329821f41940fff03c16dd1e3...
==========

[commit-bot: I haz the power, 2017-03-31 04:35:58]

Committed patchset #1 (id:1) as
https://chromium.googlesource.com/chromium/src/+/bc0329821f41940fff03c16dd1e3...