- From: Noam Rosenthal via GitHub <sysbot+gh@w3.org>
- Date: Thu, 25 May 2023 09:22:38 +0000
- To: public-css-archive@w3.org
> > Fwiw, you could also do this with the option 2 at #8683, by using wildcard URLs. I'm not convinced it's useful, but being able to do it based on particular URLs is definitely useful. > > Oh, I seem so to have missed that issue before. Reading that, I see the entire picture now: > > * Opt-in to entire concept via [[css-view-transitions-2] Declarative opt-in for cross-document navigations #8048](https://github.com/w3c/csswg-drafts/issues/8048) _(replacing `startViewTransition`, and replacing the temporary meta tag approach)_ > * Use same `view-timeline-name` declarations > * Tweak animation type via [[css-view-transitions-2] MPA: Reacting to the old/new page type #8683](https://github.com/w3c/csswg-drafts/issues/8683) _(replacing setting of classes)_ > > Will chime in on #8683, as that better addresses [my last question _(number 5)_ earlier in this thread](https://github.com/w3c/csswg-drafts/issues/8868#issuecomment-1560062850) Yea I think I was going with this rather than #8683 because of https://github.com/w3c/csswg-drafts/issues/8683#issuecomment-1561448917 but let's continue the discussion there. closing this one for now. -- GitHub Notification of comment by noamr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8868#issuecomment-1562574388 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 25 May 2023 09:22:39 UTC