Component frameworks remove UI before exit animations can finish
When a state change removes a component, its framework may remove it from the render tree before its exit animation can play. The signals describe Blazor developers duplicating animation timing in CSS and application code or writing custom logic, alongside an Angular request for a pre-destruction hook. These are older feature requests, so current framework support and demand need validation.
For blazor and Angular developers building animated interfaces. Mentioned from Apr 2018 to Sep 2019 on GitHub.
3 different people described this problem in 2 separate discussions.
- Indie fit
- 4.0/10
- Pain
- 5.5/10
- Frequency
- 5.0/10
- Willingness to pay
- 0.0/10
- Momentum
- 5.0/10
- Who pays
- Professionals
- Competition
- Medium
- Build difficulty
- Medium
What people said
Quoted word for word. Follow a link to read the whole discussion.
Introduce the concept of state transitions in Blazor to allow for e.g. animations @SteveSandersonMS > , and incorporates logic to delay the removal of each item so it can be animated out.
Animating adding a component can be done with CSS, but I think that animating the removal of a component will be impossible because it simply doesn't exist in the next render, so there's nothing to hang the animation onto?
Build brief
See what to build and who will buy it
- 1 product idea with the smallest useful version and pricing
- 4 places to find your first customers
- 2 more quotes from people who have this problem
- Current workarounds, existing solutions and risks