- From: CSS Meeting Bot via GitHub <noreply@w3.org>
- Date: Wed, 28 Jan 2026 17:20:09 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed ``[css-navigation-1] Allow `navigation-param()` to specify whether it should read params from the old/new/current URL``, and agreed to the following:
* `RESOLVED: specify from/to and this/other for navigation-param(), at least for now, and add examples`
<details><summary>The full IRC log of that discussion</summary>
<emilio> bramus: right now navigation-param() gets one argument which is the named param<br>
<emilio> ... If you're going from details page to another details page, sometimes you want to know the id from the old or the new page<br>
<emilio> ... so you can style things differently<br>
<emilio> q+<br>
<emilio> ... there's an example there in the issue<br>
<astearns> ack romain<br>
<emilio> ... it'd be handy to know what was the ID in the older page<br>
<emilio> ... so proposal would be to add a param to distinguish between old / new<br>
<emilio> ... noamr raised that you might want to specify<br>
<emilio> ... but also should we specify from / to rather than "the other page"<br>
<fantasai> scribe+<br>
<astearns> ack emilio<br>
<fantasai> emilio: What's the intended behavior when something like restoring your session?<br>
<fantasai> emilio: For View Transitions you wouldn't trigger a transition, no problem<br>
<fantasai> emilio: But these selectors are more general, maybe you're styling color or whatever<br>
<fantasai> emilio: So it seems weird if I get different behavior when closing/opening window<br>
<fantasai> bramus: If you reopen, there's no navigation<br>
<fantasai> noamr: Semantics for this follow the navigation API semantics<br>
<fantasai> noamr: what is the current navigation, etc.<br>
<fantasai> dbaron: Navigation_param() will only have values while a navigation is in progress<br>
<fantasai> emilio: Oh, ok<br>
<fantasai> bramus: The examples are always wrapped in @navigation, which targets an ongoing navigation<br>
<lea> q?<br>
<fantasai> dbaron: That said, :link-to() could be used without navigation param<br>
<lea> q+<br>
<fantasai> dbaron: So it could be used when a navigation is not in progress<br>
<fantasai> dbaron: but in that case you can't use navigation_param<br>
<fantasai> emilio: I understand for view transitions it's what you want<br>
<iank_> Ding ding<br>
<iank_> Dong*<br>
<fantasai> emilio: But if you want, e.g. when I navigate from this page I want the link to be bigger... and then it stops matching, maybe that's confusing?<br>
<fantasai> ChrisL: Is this matching / not-matching defined in terms of ???<br>
<fantasai> ChrisL: Defines partial availability of previous page<br>
<fantasai> emilio: defined in terms of Navigation API, which is hopefully reasonably well-defined<br>
<fantasai> dbaron: The spec has a few issues about getting that integration right<br>
<fantasai> dbaron: But these are issues that are at a pretty detailed level<br>
<fantasai> dbaron: Need to do some spec editing to make it tight<br>
<fantasai> dbaron: IIRC, in the old page you don't really ever see the styles with these matching, but you take View Transition snapshots at that time. Or something.<br>
<fantasai> noamr: Starts navigate event, that is when you click the link,<br>
<fantasai> noamr: Once you're ready for cross-document view transitoin, then ??<br>
<fantasai> noamr: The styles last until the first frame of the next document or end of view transition<br>
<astearns> ack lea<br>
<fantasai> lea: Common to have different types of effects depending on where you're from<br>
<fantasai> emilio: Yes, but it stops matching once you finished the transition<br>
<fantasai> noamr: :link-to() will work, but navigation_param() won't work<br>
<fantasai> noamr: :link-to() is just url pattern matching without<br>
<fantasai> emilio: Forget about view transitions, have a selector :link-to( navigation_param(old_id1))<br>
<fantasai> emilio: When I navigate from that page to my page, maybe the link is bold<br>
<fantasai> emilio: but then once navigation ends it's no longer bold<br>
<emilio> lea: so this navigation-param() thing takes the param from the current url<br>
<emilio> emilio: only during the navigation AIUI, tho<br>
<emilio> lea: then what I wanted to say doesn't apply<br>
<emilio> astearns: the point of this issue is distinguishing whether we need to distinguish old and new<br>
<emilio> ... sounds like the answer is yes<br>
<emilio> bramus: I have a view-transition example<br>
<bramus> https://view-transitions.chrome.dev/profiles/mpa/<br>
<emilio> ... there's specific in pageswap and pagereveal<br>
<emilio> ... I'm extracting values from both ends<br>
<emilio> q+<br>
<emilio> ... I had to use js for this back in the day<br>
<astearns> ack dbaron<br>
<emilio> dbaron: I think we discussed two different pairs of concepts<br>
<emilio> ... old vs. new page<br>
<emilio> ... and "this vs. other page"<br>
<emilio> ... we should probably put both for now but this vs. other might be the more important pair<br>
<emilio> dbaron: when you navigate to the new page is the page you navigate to<br>
<emilio> ... but the reason to care for this vs. other is so the animation can easily be symmetric<br>
<fantasai> scribe+<br>
<fantasai> emilio: So this page will match basically both pages of the navigation?<br>
<fantasai> emilio: at different times<br>
<fantasai> emilio: If I havigate from A to B, "this page" will match both the old and new page<br>
<fantasai> emilio: the old page while navigating away, and new page while navigating into?<br>
<fantasai> dbaron: Depends where style is writte<br>
<fantasai> dbaron: In page A, it's talking about itself. In page B, it's talking about other<br>
<fantasai> bramus: In examples, @navigation rule is used for that<br>
<fantasai> bramus: e.g. @navigation from A to B { ... }<br>
<fantasai> bramus: There's a navigation at() as well<br>
<fantasai> emilio: Agree with dbaron that it makes more sense<br>
<fantasai> emilio: New vs old is confusing<br>
<fantasai> emilio: Seems hard to reason about<br>
<dbaron> s/it makes/this versus other makes/<br>
<fantasai> ChrisL: Current page could be page I'm defined in, vs page I'm viewing<br>
<fantasai> bramus: fwiw, the terminology is "from" and "to"<br>
<fantasai> dbaron: We also have side issue on making @navigation better at doing things symmetrically<br>
<fantasai> dbaron: Commonly want to do vice versa navigation<br>
<fantasai> bramus: next issue on the agenda!<br>
<fantasai> astearns: So suggestion here is to specify both old and new, and this and other?<br>
<fantasai> astearns: And see if in the end we need them all?<br>
<fantasai> bramus: from and to, to match @navigation terminology<br>
<dbaron> PROPOSED: specify from/to and this/other for navigation-param(), at least for now, and add examples<br>
<noamr> at: and with:<br>
<fantasai> fantasai: this/other or here/there? :)<br>
<emilio> RESOLVED: specify from/to and this/other for navigation-param(), at least for now, and add examples<br>
<dbaron> (with this/other names to be bikeshedded)<br>
</details>
--
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13179#issuecomment-3812698531 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 28 January 2026 17:20:11 UTC