Intent to Prototype: Navigation API: NavigateEvent delayed commit capability

[Nate Chapin]

Contact emails

jap...@chromium.org, dom...@chromium.org

Explainer

https://github.com/WICG/navigation-api#manual-commit

Specification

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>History

Motivation

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/66

TAG review

TAG review status

Pending

Risks

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

Is this feature fully tested by web-platform-tests?

Yes

Flag name

Requires code in //chrome?

False

Estimated milestones

No milestones specified

Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/5134734612496384

This intent message was generated by Chrome Platform Status.