Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for view-transition-name #41

Open
mrbjjackson opened this issue Nov 6, 2024 · 2 comments
Open

Support for view-transition-name #41

mrbjjackson opened this issue Nov 6, 2024 · 2 comments

Comments

@mrbjjackson
Copy link

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

@mrbjjackson
Copy link
Author

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?

Thanks

@kevinmatr
Copy link

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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants