Oh very cool! Seems pretty small / low risk to me, LGTM1 with a couple minor points below.
On Thu, Sep 3, 2026 at 5:46 AM Chromestatus <[email protected]> wrote: > *Contact emails* > [email protected], [email protected] > > *Explainer* > > https://github.com/WICG/declarative-partial-updates/blob/main/route-matching-explainer.md#link-matching > > *Specification* > https://drafts.csswg.org/css-navigation-1/#navigation-source-pseudo-class > > *Summary* > Selects the element that initiated the navigation, whether it's a > link/button/form. The element stays selected throughout the navigation. > > *Blink component* > Blink>CSS > <https://issues.chromium.org/issues?q=customfield1222907:%22Blink%3ECSS%22> > > *Web Feature ID* > Missing feature Thanks for filing the new feature request <https://github.com/web-platform-dx/web-features/issues/4301>, looks like there's some questions there to follow up on. This is important for coverage in webstatus.dev etc. Think it's OK for feature available of all of CSS navigation to be grouped together, or might some devs (or agents) want to reason about the navigation-source feature availability independently from the rest? *Motivation* > The main motivation for this comes from view transitions. This gives > author a way to visually indicate a relationship between the navigation > source (form/button) and the process of the navigation, e.g. expanding a > thumbnail using an animation. > > *Initial public proposal* > https://github.com/w3c/csswg-drafts/issues/11801 > > *TAG review* > *No information provided* Added the link to your chromestatus entry: https://github.com/w3ctag/design-reviews/issues/1253 > *TAG review status* > Pending *Goals for experimentation* > None > > *Risks* > > > *Interoperability and Compatibility* > *No information provided* > > *Gecko*: No signal ( > https://github.com/mozilla/standards-positions/issues/1447) > > *WebKit*: No signal ( > https://github.com/WebKit/standards-positions/issues/715) > > *Web developers*: Strongly positive (https://adactio.com/links/22686) “I > really, really, really like this proposal! This would absolutely > turbo-charge cross-document view transitions with nary a line of JavaScript > in sight.” (This is a view on the entire CSS Navigation Matching spec in > total, not `:navigation-source` individually) > > *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 > css/css-navigation/tentative/navigation-source-*.html > > *Flag name on about://flags* > *No information provided* > > *Finch feature name* > NavigationSourcePseudoClass > > *Rollout plan* > Will ship enabled for all users > > *Requires code in //chrome?* > False > > *Tracking bug* > https://issues.chromium.org/issues/530210946 > > *Estimated milestones* > Shipping on desktop 156 > Shipping on Android 156 > Shipping on WebView 156 > > *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). > None > > *Link to entry on the Chrome Platform Status* > https://chromestatus.com/feature/6327898878377984?gate=6247925882683392 > > 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/6a9941cf.aec07b4f.8d5be.0061.GAE%40google.com > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/6a9941cf.aec07b4f.8d5be.0061.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/CAFUtAY_iN87tZyB1Zf97m2J-Yo2csRK8b_N%2BMNUGbEjSVq6MsA%40mail.gmail.com.
