- From: Sebastian Zartner via GitHub <sysbot+gh@w3.org>
- Date: Sat, 05 Aug 2023 20:02:06 +0000
- To: public-css-archive@w3.org
> Option 1 implies that transitions will be enabled for reloads by default.
You mean `cross-document-same-origin-navigation` implies that? What if that explicitly excluded reloads? Then we can add a `reload` keyword to `transition-trigger`. A separate `reload` descriptor doesn't seem useful as reloads are meant to be _a type of_ transition trigger. And some combinations of `transition-trigger` and `reload` like `transition-trigger: none; reload: allow;` don't make much sense.
So the whole syntax would then look like this:
```css
@view-transition {
transition-trigger: [ same-document-navigation || cross-document-same-origin-navigation || same-site-navigation || script || reload ] | none;
}
```
Sebastian
--
GitHub Notification of comment by SebastianZ
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8048#issuecomment-1666593022 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 5 August 2023 20:02:08 UTC