Call onPageStarted, onPageFinished for HTTP-error error pages
Previously HTTP errors will not result in an error page being committed immediately (instead the renderer will trigger an error page navigation after the original committed navigation), so onPageStarted and onPageFinished will be called for http error navigations. After crrev.com/c/2487024, it's possible for navigations with an error HTTP status code and an empty response body to immediately result in an error page navigation. In this case, we should ensure that we still call onPageStarted and onPageFinished to be consistent with other HTTP error cases. Bug: 1147227 Change-Id: I595c411ef61bd8bb8c6b2bf2779b7b29ef18dd07 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2528511Reviewed-by:Bo <boliu@chromium.org> Reviewed-by:
Nate Fischer <ntfschr@chromium.org> Commit-Queue: Rakina Zata Amni <rakina@chromium.org> Cr-Commit-Position: refs/heads/master@{#826050}
Showing
Please register or sign in to comment