- From: Noam Rosenthal via GitHub <sysbot+gh@w3.org>
- Date: Thu, 28 Sep 2023 06:49:45 +0000
- To: public-css-archive@w3.org
You're right that redirects might make it so that a reload doesn't necessarily mean the same URL/origin, so perhaps it needs to be `@view-transition same-origin reload`.
About the qualifiers, I'd prefer to look at them more from a user intent standpoint rather than from technical history/navigation terms like push/replace.
"reload" and "back" are clear user experience intents, also "forward", "jump to some place in history", or "jump to a random URL in this origin" (address bar, bookmark, extension etc), and of course a normal navigation like links/forms.
The way I see it, the opt-in rule applies to some of these intents. By default, probably to navigate+forward+back, and arguably jump. It applies to reload only if explicit. So
`@view-transition same-origin` actually means something like `@view-transition (navigate or back or forward) from urlpattern("/*") to urlpattern("/*")` and @view-transition same-origin reload` means `@view-transition (reload) from urlpattern("/*") to urlpattern("/*")`. We can perhaps keep the same-origin implicit when reload is present, but I'm not sure we have to decide on this now. Perhaps this discussion can continue in #8784? Not sure it affects the default opt-in that much.
--
GitHub Notification of comment by noamr
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8048#issuecomment-1738565536 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 06:49:46 UTC