- From: Sebastian Zartner via GitHub <sysbot+gh@w3.org>
- Date: Wed, 09 Aug 2023 17:03:54 +0000
- To: public-css-archive@w3.org
As I understand it, the point of the `@view-transition` rule as it was initially proposed is to configure _under which conditions_ view transitions should be triggered.
It does _not_ cover different view transitions based on those conditions. If there should be different transitions for different conditions, we need a separate feature to detect that.
New media features lend themselves to target this use case. Though _if_ we go that route, I'd suggest to keep them general and only bind them to navigation, not view transitions specifically.
So we'd introduce media features like `navigation-type: [ reload | push ]`, `navigation-origin: [ same-origin | cross-origin ]` (plus maybe URL patterns) and `navigation-mechanism: [ interaction | api ]`.
So a media query could then look like this:
```css
@media (navigation-type: reload) or (navigation-origin: cross-origin) {
…
}
```
Sebastian
Sebastian
--
GitHub Notification of comment by SebastianZ
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8048#issuecomment-1671820492 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 9 August 2023 17:03:56 UTC