Re: [csswg-drafts] [css-view-transitions-2] Support same-site cross-origin view transitions (#10364)

<thoughts>
A path forward to allowing this could be to expand on what we can do declaratively, and then restrict the JS access to the transition if it's cross-origin.

In essence, do the following:
- Introduce something like #8925 where the view-transition can be enabled/customized (using `types`) based on which origin it's going to
- Both sides have to explicitly opt-in to a view-transition for that particular origin
- Perhaps even limit this to first-party-sets, and gate by referrer policy. This addresses other issues such as user confusion about "which origin am I on" and issues like passing side-channel information inside a view-transition list of captured elements.
- View transitions would have to be expressive enough without old-document script access to the post-redirect origin, and without a web-visible extra rendering cycle that captures the view transition.
- I'm not sure if we can/want to support cross-origin back/forward navigations. Perhaps the default for cross-origin navigations should be ordinary navigations and one has to explicitly add `traverse` as a type to `@view-transition`

-- 
GitHub Notification of comment by noamr
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10364#issuecomment-2220692518 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 10 July 2024 14:37:05 UTC