Contact emails
jap...@chromium.org, dom...@chromium.orgExplainer
https://github.com/WICG/navigation-api#manual-commitSpecification
Summary
Normally, when navigateEvent.intercept() is called, the intercepted navigation commits (and therefore the URL updates) as soon as the NavigateEvent finishes dispatch. This adds a `commit` option to navigateEvent.intercept(). If a `commit` value of "manual" is given, the commit will be deferred until the new navigateEvent.commit() method is called.
Blink component
Blink>HistoryMotivation
In developing the navigation API, we heard feedback (https://github.com/WICG/navigation-api/issues/66) that our current policy of immediately committing the navigation does not match with how routing libraries currently model asynchronous same-document navigations.
Initial public proposal
https://github.com/WICG/navigation-api/issues/66TAG review
TAG review status
PendingRisks
Interoperability and Compatibility
Gecko: No signal
WebKit: No signal
Web developers: Strongly positive (
https://github.com/WICG/navigation-api/issues/66) Developers are clear that this capability is desired and useful, with the cited issue containing several example use cases. During the Dev Trial we intend to validate that the proposed API shape works well for them.
Other signals:
WebView application risks
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
Debuggability
YesFlag name
Requires code in //chrome?
FalseEstimated milestones
No milestones specified
Link to entry on the Chrome Platform Status
https://chromestatus.com/feature/5134734612496384