👀 React <ViewTransition> + DOM moveBefore()
- moveBefore() now allows React to preserve state during siblings reconciliation (experimental channel)
- you can animate those stateful elements with <ViewTransition>
Quite cool 😁
oh awesome! That's an old one ... framer-motion 1.6! 😅
In other words, Design Systems are Platform on the experience design side. I’ve been advocating for this mindset shift for the last few years, and this excellent article by Sam Anderson provides a fantastic overview of why. www.linkedin.com/pulse/design...
one of the great things about react-aria is that if one abstraction doesn't work for you (say, useGridList), you can always reach for a lower abstraction. With most libraries, you need to either opt-in entirely, or build from scratch.
making some updates to our carousel
- built upon react-aria collections / keyboard controls / selection mechanics
- entrance / exit animations
- scroll masking under the arrow buttons
oh wow, i thought it was just elon posts these days. might need to check it out again
exit animations with the view transitions api:
::view-transition-old(.card):only-child {
animation: 300ms ease both fade-out;
}
... that's it. In React, this is so nice: no more `cloneElement` or array slicing.
This please
Great advice! Thank you!
Well done! Since having a kid I’ve found it very difficult to find any time to exercise. Any tips?
there should be an app that exposes you to the schemes and machinations of weirdos
don’t useEffect, but if you must, don’t call setState in it
oh no ... the video quality is even worse than twitter... 😩
in my opinion, a list component shouldn't animate when filtering via something like a search input, but it should animate when delete / add mutations occur. at frame, our list component has this behavior built in
