- From: Khushal Sagar via GitHub <sysbot+gh@w3.org>
- Date: Thu, 28 Sep 2023 18:06:31 +0000
- To: public-css-archive@w3.org
Sorry I'm still not following how we're dealing with the combination of nav type + from/to url. Every combination of these 2 is possible. So if an author has CSS like:
```
@view-transition same-site {
trigger: navigation;
}
@view-transition reload {
trigger: navigation;
}
```
What happens if there is a reload which results in a same-site navigation? Your comment above sounds like all the qualifiers are a combination of nav type and from/to url. "same-origin" means any same-origin url of type "navigate", "back" and "forward". Presumably "same-site" would cover the same nav types. And "reload" means only same-origin reload navigations?
> We can perhaps keep the same-origin implicit when reload is present, but I'm not sure we have to decide on this now.
Asking this right now because IMO "same-origin" should only be about the from/to url. Overloading the nav type into it is not a good idea. So I'd expect `@view-transition same-origin { trigger: navigation; }` to include reloads.
--
GitHub Notification of comment by khushalsagar
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8048#issuecomment-1739788210 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 28 September 2023 18:06:33 UTC