- From: Noam Rosenthal via GitHub <sysbot+gh@w3.org>
- Date: Wed, 09 Aug 2023 17:04:58 +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> ]#;
> }
> ```
On second thought, thinking of what @fantasai brought up about specificity, I think perhaps we should go with reload (but not back-forward) in the opt-in. It means we can't customize the transition based on whether this is a reload, but at least it makes the whole specificity thing a lot simpler and perhaps customizing based on reload/not-reload is not an important use-case to begin with.
--
GitHub Notification of comment by noamr
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8048#issuecomment-1671821923 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:05:00 UTC