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/motion
Re:Enable CORS for Your Blog
by trick-or-treat on Monday March 02, 2026 @05:06AM
(#47215927)
I 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
Would also be great if the animations respected the `prefers-reduced-motion` setting, instead of forcing down animations that reduces accessibility.
Is 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/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?
Re:Enable CORS for Your Blog
by elliotbnvl on Monday March 02, 2026 @09:30AM
(#47218395)
This is something Opus 4.6 likes to generate a LOT for some reason.
In my opinion, that’s a bigger problem than CORS. Proxyless web feed reader is a lost cause, you’re wasting your time because only a small minority are ever going to support it. But that opacity and transition nonsense gratuitously slows down page loading for everyone, and hides content completely for those that aren’t running JS.
(What I would also like to know is: how come this is the third time I’ve seen exactly this—each block of content having this exact style attribute—in the past month, when I don’t remember encountering exactly it before?)