- From: CSS Meeting Bot via GitHub <noreply@w3.org>
- Date: Wed, 28 Jan 2026 17:25:20 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed ``[css-navigation-1] Simplify `@navigation` matching between two pages, regardless of direction``, and agreed to the following: * `RESOLVED: Add between with space-separated arguments` <details><summary>The full IRC log of that discussion</summary> <fantasai> bramus: This issue is about @navigation matching regardless of direction<br> <emilio> bramus: this about @navigation matching between two pages regardless of direction<br> <fantasai> bramus: Currently you can say @navigation (from: a) (to:b), but often want opposite directions.<br> <noamr> q+<br> <fantasai> bramus: Proposal is to add a new keyword "between"<br> <astearns> ack emilio<br> <fantasai> bramus: Then question is, is it comma-separated, space-separated, etc.<br> <noamr> q-<br> <emilio> fantasai: shouldn't be comma separated<br> <astearns> ack fantasai<br> <emilio> ... space or slash<br> <emilio> ... but comma seems wrong<br> <emilio> ChrisL: we use comma to separate alternates<br> <emilio> ... and this is a to b or b to a<br> <emilio> fantasai: not really, we use it to separate stacks of things<br> <TabAtkins> We use it to separate *repetitions* of things, whether they're "stacked" or not<br> <emilio> ... fonts, counters, etc<br> <emilio> bramus: space separated seems better<br> <fantasai> +1 TabAtkins<br> <TabAtkins> i think it looks reasonable for space-separated here<br> <fantasai> PROPOSED: Add between with space-separated arguments<br> <fantasai> RESOLVED: Add between with space-separated arguments<br> <fantasai> ChrisL: Presumably you can't have all three, right?<br> <fantasai> bramus: You can combine multiple conditions. And you can use boolean logic, like MQ<br> <fantasai> bramus: So you could write [...] which will parse but not match<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13199#issuecomment-3812726459 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:25:21 UTC