LGTM2 Opinion on web feature ID inline:
On Tue, Sep 8, 2026 at 11:34 PM Rick Byers <[email protected]> wrote: > 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? > Although it looks like :navigation-source could be used independent of the other things in the spec, I would still leave https://github.com/web-platform-dx/web-features/issues/4301 as a single request and leave it to web-features maintainers whether to create one or more web-feature IDs for this. I would predict that this gets created as a single feature, it's often the case that a feature (from a web dev PoV) ships over several Chrome versions as we're responding to feedback, but it's not that useful to capture this granularity long term. But this is a call that web-features maintainers can make. Thanks for filing the issue! -- 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/CAARdPYc65vm%3DpN-5drWigHuDu%2BpQgN_zO3FejyoKyBEGSzNsog%40mail.gmail.com.
