- From: David Bokan via GitHub <sysbot+gh@w3.org>
- Date: Wed, 15 Nov 2023 03:14:00 +0000
- To: public-css-archive@w3.org
> The fundamental difference here is whether we want types to be a source of information passing from the old page to the new. If we don't care about this channel of information +1. I was thinking that type would be how incoming and outgoing pages sync up on their states and coordinate on matching transition styles but as long as the alternatives are ergonomic then I now agree it doesn't make sense to have the types between documents interact. > authors can easily still do option 2 (union) by using NavigationHistoryEntry's [getState](https://developer.mozilla.org/en-US/docs/Web/API/NavigationHistoryEntry/getState) API. Hmm, since there's no Javascript API, are you thinking authors will use CSSOM to insert the appropriate `@view-transition` (or modify an existing) rule? I suspect this might be non-trivial in complex cases given they might have to pick out the correct one manually. Maybe we need a better way to do this? (or maybe I'm missing an existing option) <details> <summary>additional tangential replies</summary> > The difference between SPA/MPA is that with SPA authors can initiate the transition once all relevant info about the new state is known. But that's not always possible with MPA. So the model for setting types needs to diverge here. Right, forgot the fetch can (and _should_) happen before calling `startViewTransition`, rather than inside of it. > As an aside, there's another issue with option 2: it limits what names the new page can use for its types by some unknown set that the old page can specify. It seems like authors will already have to do a fair bit of coordination between pages since they'll have to make sure `view-transition-names` are coordinated between pages (and don't clash with internal state transitions), but point taken. </details> -- GitHub Notification of comment by bokand Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9526#issuecomment-1811742353 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 15 November 2023 03:14:01 UTC