mike douges
mike douges
Currently when animating an exiting component it ends up cloning the target element to keep it around for the duration of the motion (see [FocalConcealMove](https://elementmotion.com/focal-conceal-move)). This works - but leads...
- Applies motion with CSS (no JS engine) - Motion between disconnected elements - Motion between element view states - Abstract motion behind a component API - Execute multiple "motions"...
https://codesandbox.io/s/tw-04-elmo-complete-9ubiy It ends up causing too many problems. Instead of trying to be clever to try and compose them - we should just have them in one component instead. -...
All upcoming tasks that will end up being a breaking change will be consolidated here. The plan will be to keep master with v3 and keep releasing betas until it's...
Should be relatively painless (for consumers) as everything is already a render function. Defining what animations you want to happen could be tricky though. And the collector behaviour we have...
See GIF. Happens in all browsers. 
We can't easily compose things from `className` and `keyframes` ATM. Since this library wants to try and do things via CSS animation (over JS animation) we need to come up...