Re: [csswg-drafts] [css-view-transitions-2] Declarative opt-in for cross-document navigations (#8048)

My interpretation of what @noamr is saying is that we can treat `(navigation, back, forward)` as the implicit default navigation type.

I agree with @khushalsagar that my understand of same-origin is to be specifically about `from`/`to`, and not the type of getting from `from` to `to`.

The syntax that I like is something like
```
@view-transition <<route>> <<navtype>> { ... }
```
Where
```
<<route>> = '' | (from: <urlpattern> || to: <urlpattern>) | same-origin | same-site
<<navtype>> = '' | (navigation || back || forward || reload) | including-reload
```
with an explicit note that explains that if `route` is `''`, ie empty, then it is the same as same-origin; if `navtype` is empty, then it is the same as `navigation back forward`, but _not_ `reload`. I've also added `including-reload` to mean the default ones, and reload, meaning everything.

So with this syntax, I think we can express everything?
Specifically, `@view-transition same-origin` means it doesn't include reloads, and it's about going from `/*` to `/*`.

To answer @khushalsagar's question, in this syntax `@view-transition reload` means "same origin reload only". If you want to capture all same-site navigations including reloads, then that's `@view-transition same-site including-reload`.



-- 
GitHub Notification of comment by vmpstr
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8048#issuecomment-1739808346 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:22:34 UTC