LGTM3 On Mon, Dec 15, 2025 at 9:21 PM Yoav Weiss (@Shopify) < [email protected]> wrote:
> LGTM2 > > On Tue, Dec 16, 2025 at 1:42 AM Mike Taylor <[email protected]> > wrote: > >> LGTM1 >> On 12/15/25 7:06 a.m., Chromestatus wrote: >> >> *Contact emails* >> [email protected] >> >> *Explainer* >> >> https://html.spec.whatwg.org/multipage/nav-history-apis.html#dom-navigationtransition-to >> >> *Specification* >> https://html.spec.whatwg.org/#dom-navigationtransition-to >> >> *Summary* >> Currently NavigationTransition has a "from" 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. Note >> that navigation.transition is only exposed for intercepted navigations - >> which means same-origin document-initiated navigations. >> >> *Blink component* >> UI>Browser>Navigation >> <https://issues.chromium.org/issues?q=customfield1222907:%22UI%3EBrowser%3ENavigation%22> >> >> *Web Feature ID* >> navigation <https://webstatus.dev/features/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* >> *No information provided* >> >> *TAG review status* >> Pending >> >> *Risks* >> >> >> *Interoperability and Compatibility* >> *No information provided* >> >> *Gecko*: No signal ( >> https://github.com/mozilla/standards-positions/issues/1324) >> >> But, trending positive... (and supportive enough to justify merging to >> HTML). >> >> >> *WebKit*: No signal ( >> https://github.com/WebKit/standards-positions/issues/585) >> >> *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? >> *No information provided* >> >> >> *Debuggability* >> *No information provided* >> >> *Will this feature be supported on all six Blink platforms (Windows, Mac, >> Linux, ChromeOS, Android, and Android WebView)?* >> Yes >> >> *Is this feature fully tested by web-platform-tests >> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>?* >> Yes >> >> >> *Flag name on about://flags* >> *No information provided* >> >> *Finch feature name* >> NavigationTransitionDestination >> >> *Rollout plan* >> Will ship enabled for all users >> >> *Requires code in //chrome?* >> False >> >> *Tracking bug* >> https://issues.chromium.org/issues/447171238 >> >> *Estimated milestones* >> Shipping on desktop 145 >> Shipping on Android 145 >> Shipping on WebView 145 >> >> *Anticipated spec changes* >> >> Open questions about a feature may be a source of future web compat or >> interop issues. Please list open issues (e.g. links to known github issues >> in the project for the feature specification) whose resolution may >> introduce web compat/interop risk (e.g., changing to naming or structure of >> the API in a non-backward-compatible way). >> *No information provided* >> >> *Link to entry on the Chrome Platform Status* >> https://chromestatus.com/feature/6008183302782976?gate=6022234166657024 >> >> *Links to previous Intent discussions* >> Intent to Prototype: >> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/68d4ff4d.2b0a0220.29ae18.0091.GAE%40google.com >> >> >> This intent message was generated by Chrome Platform Status >> <https://chromestatus.com>. >> -- >> You received this message because you are subscribed to the Google Groups >> "blink-dev" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion visit >> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/693ff9cc.050a0220.2e69e1.0294.GAE%40google.com >> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/693ff9cc.050a0220.2e69e1.0294.GAE%40google.com?utm_medium=email&utm_source=footer> >> . >> >> -- >> You received this message because you are subscribed to the Google Groups >> "blink-dev" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion visit >> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/9e155776-4ce2-430b-9a60-d7ec8510c357%40chromium.org >> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/9e155776-4ce2-430b-9a60-d7ec8510c357%40chromium.org?utm_medium=email&utm_source=footer> >> . >> > -- > You received this message because you are subscribed to the Google Groups > "blink-dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOmohSLZ0dmdC2KsMdpxUopzp2CUZHaXS_%3DPt0aSb0qAADkXiQ%40mail.gmail.com > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOmohSLZ0dmdC2KsMdpxUopzp2CUZHaXS_%3DPt0aSb0qAADkXiQ%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw9Y4o9zyBxJvgxe4cXset1-51qOp-x%3DqCU-1TCvBBjaBQ%40mail.gmail.com.
