Smooth layout changes with Transition API
See original GitHub issueNew Transition
API looks like great alternative to LayoutAnimation
API, but when elements appear/disappear, we do not have smooth changes of other elements, that being affected via layout changes, even with scale
type. In case of LayoutAnimation
there is no such a problems and also in case of Transition.Change
, we also have smooth experience, the only problem is elements’ appearance/disappearance.
Any ideas on how we can mimic LayoutAnimation
’s behavior with new Transition
API?
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Smooth and simple transitions with the View Transitions API
The View Transition API makes it easy to change the DOM in a single step, while creating an animated transition between the two...
Read more >Animate layout changes using a transition - Android Developers
Animate layout changes using a transition ; Group-level animations: Apply one or more animation effects to all of the views in a view...
Read more >Smooth layout changes with Transition API · Issue #264 - GitHub
New Transition API looks like great alternative to LayoutAnimation API, but when elements appear/disappear, we do not have smooth changes of ...
Read more >Smooth Page Transitions with Astro & the Shared ... - YouTube
Smooth Page Transitions with Astro & the Shared Element Transition API. Watch later. Share. Copy link. Info. Shopping. Tap to unmute.
Read more >Shared element transitions or how to fight Cumulative Layout ...
This API allows a smooth transition between this list and a details view. The excellent article “Smooth and simple page transitions with the ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks for attention. Sure, will try to find time on a weekend to create repro snack.
We discussed Transitions internally in our team. Considering that v2 makes creating animations easier and Transitions was an experimental API for a long time, we decided to leave Transitions as they are.
We won’t actively fix bugs in them, but we’ll happily merge any PR with fixes. We’re also thinking about rewriting Transitions in v2 sometime in the future.
I’m closing this issue, but if you have further questions, I will be happy to help.