Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Properly handle non-current entries with no NavigationApi state
1. The NavigationApiHistoryEntry mojom struct doesn't allow a null string representation of the the state object, which confuses deserialization when no state object is set. 2. When the state object is updated, it does not immediately get synced to the browser process. This is because it is either set shortly after commit for ordering reasons (and so misses the sync that happens during commit), or is updated by navigation.updateCurrentEntry() (which is not treated as a navigation, so there is no commit). This is problematic because the navigation api state object can be exposed on other same-origin documents, and that state is gathered in the browser process commit logic, which is too early for the renderer's "last chance" sync during unload. When that happens, the next document's entry for for the previous document has an out-of-date state object. Introduce a mechanism to force an immediate history sync outside of the commit/freeze/unload ones, and use it when navigation api state is updated. Bug: 1326246 Change-Id: Ie62bf0791c0e366258a32a5e62f193d5597de5a7 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3662189 Reviewed-by: Charlie Reis <[email protected]> Reviewed-by: Domenic Denicola <[email protected]> Reviewed-by: Daniel Cheng <[email protected]> Commit-Queue: Nate Chapin <[email protected]> Cr-Commit-Position: refs/heads/main@{#1008064}
- Loading branch information