- From: Noam Rosenthal via GitHub <sysbot+gh@w3.org>
- Date: Sat, 30 Sep 2023 06:41:47 +0000
- To: public-css-archive@w3.org
> > We're not suggesting the qualifiers yet. But I imagine having and/or/() like media queries.
>
> It's likely fine, I'm just convincing myself that we'll be able to add both and/or operators with the qualifiers later. For example, having no qualifiers implicitly expands to both default values + "and" operator between them. But the author will be able to override the defaults by providing an explicit value for each qualifier + whether its "and"/"or".
>
> ```css
> @view-transition { ... }
>
> /* The above expands to the following */
> @view-transition <<route>> and <<navtype>> and /* any other potential qualifiers */ { ... }
What are the other potential qualifiers?
>
> @view-transition <<route>> or <<navtype>> { ... }
I think this would expand to `(<<route>> and <<default-nav-types>>) or (<<navtype>> and same-origin)
--
GitHub Notification of comment by noamr
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8048#issuecomment-1741695878 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 30 September 2023 06:41:49 UTC