UserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.104 Safari/537.36

Steps to reproduce the problem:
1. Have a new webview on some valid page.
2. Navigate webview to some invalid page (e.g. webview.src="https://www.blablablabla.bla")
3. Wait for webview to finish (e.g. to "loadstop" event)
4. Call "canGoBack()" function on webview. It will return false. But "back()" function will navigate back anyway.

What is the expected behavior?
"canGoBack()" function on webview returns proper value. If true navigation back is indeed possible and vice versa.

What went wrong?
"canGoBack()" returns false when navigated to invalid page (if there is just one previous page).

Did this work before? Yes 55

Does this work in other browsers? Yes

Chrome version: 59.0.3071.104  Channel: n/a
OS Version: 6.1 (Windows 7, Windows Server 2008 R2)
Flash Version: 

In attached example (chrome unpacked extension) there is webview on valid page (google.com). With "Go!" button you will navigate to invalid page ("https://www.blablablabla.bla"). You can see "webview-canGoBack" button is disabled (because webview.canGoBack() returns false). If you call "back()" function anyway via "webview-back" button it will navigate back. if you will navigate to valid page "webview-canGoBack" button will be enabled.

The reason is that in "DidFinishNavigation" function (extensions/browser/guest_view/web_view/web_view_guest.cc see link to related commit below) doesn't dispatch "webview::kEventLoadCommit" event in case of error page. One of the easier fixes in my eyes, hopefully will be fixed soon in chromium upstream.

Issue was introduced here:
related review:
https://codereview.chromium.org/2411293002

related commit:
https://chromium.googlesource.com/chromium/src/+/6adb8c23bd7b3fe24398c5500a2f89c758e36a4d
 

Deleted: example.zip 1.6 KB

example.zip 1.6 KB Download