Intent to Prototype: Navigation API: expose destination in navigation.transition

[Chromestatus]

Contact emails

nrose...@chromium.org

Explainer

None

Specification

https://github.com/whatwg/html/pull/11692

Summary

Currently NavigationTransition has a "for" property, exposing the old URL of the navigation. Exposing "to" (a NavigationDestination) completes this. It is especially useful when using precommit handlers, as during precommit the current URL has not yet switched to the destination.

Blink component

UI>Browser>Navigation

Web Feature ID

navigation

Motivation

Exposing things in navigation.transition helps curating the navigation experience without having to listen to *all* navigation events. Specifically, the to/from properties of navigation.transition map nicely to the to/from route matchers (see https://github.com/WICG/declarative-partial-updates/blob/main/route-matching-explainer.md)

Initial public proposal

https://github.com/whatwg/html/pull/11692

TAG review

None

TAG review status

Pending

Risks

Interoperability and Compatibility

None

Gecko: No signal

WebKit: No signal

Web developers: No signals

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? None

Debuggability

None

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

Yes

Flag name on about://flags

NavigationTransitionDestination

Finch feature name

None

Non-finch justification

None

Requires code in //chrome?

False

Tracking bug

https://issues.chromium.org/issues/447171238

Estimated milestones

No milestones specified

Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/6008183302782976?gate=5100687448997888

This intent message was generated by Chrome Platform Status.