- From: Noam Rosenthal via GitHub <sysbot+gh@w3.org>
- Date: Wed, 09 Aug 2023 16:31:28 +0000
- To: public-css-archive@w3.org
> It seems a little strange for reloads, specifically, to be handled differently than other trigger qualities; it seems to be just as much a quality of the trigger as "same-origin" vs "cross-origin", I think? I suggest baking this into the trigger syntax itself, and using comma separation, like:
>
> ```
> @view-transition {
> transition-trigger: none | [ [ reload | no-reload ] || <transition-type> ]#;
> }
> ```
It's a different quality from same-document/cross-document, as reload could be either.
Also, a reload is something that might call for a different customization (class/group), e.g.:
```css
@view-transition :reload {
navigation-trigger: cross-document-same-origin;
/* this would be available in MQs to customize the transition */
transition-group-name: reloading;
}
```
--
GitHub Notification of comment by noamr
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8048#issuecomment-1671760932 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 16:31:29 UTC