- From: Noam Rosenthal via GitHub <sysbot+gh@w3.org>
- Date: Sun, 11 Jun 2023 07:11:12 +0000
- To: public-css-archive@w3.org
> > In case of transitioning-from-blank, what's the advantage of view transitions? There's no detailed "old" state which is where VT can do things regular css animations can't. The developer can use regular keyframe animations, and reuse animation names with VT. > > Generally, the answer is simplicity. It's a similar answer to why have SPA view transitions. Entry animation with only "opt in to view transitions" is easier than any particular keyframe / animation set up that the developer could do. What would you be opting in to? Entry animations don't have an "old" state so they're inherently different in most cases than the old->new animations. To make them meaningful, you'd have to define keyframes especially for this case, e.g. to slide-in an element from "somewhere" rather than from the previous location. If you do that, why not just set those keyframes on the element itself rather than rely on captures and a new syntax? > > I'm also fine with not doing the transition, if that's easier, I was mostly wondering if there is a use-case here that could be easily solved. Do you have an existing page to play with a use-case? I want to see if the current solution is lacking (applying keyframes on the actual element when there is no view-transition). -- GitHub Notification of comment by noamr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8791#issuecomment-1586048290 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 11 June 2023 07:11:14 UTC