commit 983a483cfa2c2c6662190d8ff58316244a573067
author Nate Fischer <ntfschr@chromium.org> Tue Jan 09 21:41:16 2018
committer Commit Bot <commit-bot@chromium.org> Tue Jan 09 22:39:49 2018
tree 71f9cd3896dd179d5bfc9bffc9ca231ba6aa9dfb
parent a3ba62ce1075de9b6c9a4db48cd12d001ca24b97

AW: regression test for loadUrl within shouldOverrideUrlLoading

No change to production logic, this only tests an already-fixed
scenario.

This tests a common pattern for apps to use: cancel a navigation in
shouldOverrideUrlLoading, but reload the same URL with a call to
loadUrl() (this is usually done to append custom headers to render
initiated navigations, but it reproduces with a simple loadUrl() too).

Applications previously observed that the back-forward history breaks,
since the canceled-and-reloaded URL doesn't appear as a history entry.
This test ensures that canGoBack() and goBack() behave sensibly.

Bug: 794020
Test: run_webview_instrumentation_test_apk -f AwContentsClientShouldOverrideUrlLoadingTest#testReloadingUrlDoesNotBreakBackForwardList
Change-Id: I51aa11d01d47d8e23f4dc7a35478d20a4354e45a
Reviewed-on: https://chromium-review.googlesource.com/855643
Commit-Queue: Nate Fischer <ntfschr@chromium.org>
Reviewed-by: Bo <boliu@chromium.org>
Cr-Commit-Position: refs/heads/master@{#528142}