You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for making this.
I've successfully got the simple "fading" transition working. However one of the joys of using this in other frameworks was that you could simply give an element a "view-transition-name" id property on one page and the same property on the following page and the browser would attempt to seamlessly transition between them.
As far as I can tell this doesn't work with this package yet? Am I right about this? Has anyone else had any joy getting it to work?
Thanks,
Ben
The text was updated successfully, but these errors were encountered:
Update: I have since produced a super simple 2 page navigation reproduction and I see that the "view-transition-name" is indeed working, however on my production app it is not.
I assume this is because there is more complicated stuff (e.g. async data fetching, caching?) going on. Any tips on getting these view transitions to work on "heavier" pages?
Facing the same issue, I think this feature wasn't work so well with non-static page.
With dynamic route, transition doesn't show up while entering a route for the first time. But the transition shows without a problem after it(calling browser's back or forward).
Thanks for making this.
I've successfully got the simple "fading" transition working. However one of the joys of using this in other frameworks was that you could simply give an element a "view-transition-name" id property on one page and the same property on the following page and the browser would attempt to seamlessly transition between them.
As far as I can tell this doesn't work with this package yet? Am I right about this? Has anyone else had any joy getting it to work?
Thanks,
Ben
The text was updated successfully, but these errors were encountered: