Do not change BrowsingInstance on error page commits.
When error page isolation is enabled, error pages commit in their own SiteInstance. Reloading an error page should stay in the same SiteInstance it was initially placed in. However, if a navigation is to an URL that requires a BrowsingInstance swap, forcing the swap causes the error page to commit in a SiteInstance for the destination URL. This is not expected nor is it the desired behavior. This CL adds a check for error pages in ShouldSwapBrowsingInstancesForNavigation to keep the commits in the same BrowsingInstance. When a successful navigation/reload happens for the destination URL, the BrowsingInstance will be correctly swapped. Bug: 838161 Change-Id: Iaf2e708426b75881dda7065069b618f180fef7d2 Reviewed-on: https://chromium-review.googlesource.com/1113905 Commit-Queue: Nasko Oskov <nasko@chromium.org> Reviewed-by:Alex Moshchuk <alexmos@chromium.org> Cr-Commit-Position: refs/heads/master@{#570251}
Showing
Please register or sign in to comment