3 ms·
The entire web app is JS based. It's a requirement I'm ok with. And to answer your question, you're seeing that kind of styling so frequently because it's like
by travisvn 7mo ago
The entire web app is JS based. It's a requirement I'm ok with.
And to answer your question, you're seeing that kind of styling so frequently because it's likely part of Framer Motion, an extremely popular animation library
https://www.npmjs.com/package/framer-motion https://www.npmjs.com/package/framer-motion
https://www.npmjs.com/package/motion https://www.npmjs.com/package/motion
- trick-or-treat 7mo agoI think cooler heads will agree that a middle ground where the content is available on the initial request is best. But what do I know /s
- Orygin 7mo agoWould also be great if the animations respected the `prefers-reduced-motion` setting, instead of forcing down animations that reduces accessibility.
- mzajc 7mo agoIs the website machine generated? Besides the hard-dependency on JavaScript, this also causes the exact same problem I've seen on another[1] machine generated site: https://postimg.cc/TyMBfVZ6 https://postimg.cc/TyMBfVZ6, https://postimg.cc/n9j1X5Dk https://postimg.cc/n9j1X5Dk. This happens randomly on refresh on Firefox 148.0-1. Is the fade effect really worth having parts of your site disappear at random? [1] https://news.ycombinator.com/item?id=46675669 https://news.ycombinator.com/item?id=46675669