You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, this is not an issue, i just wanted to share experience :)
I have one old project where I use MDBootstrap and WOW.js.
Suddenly on scroll effects stoped working on some stations - no errors, console log is empty
There is this settings in Windows 11 called "Animation effects". When it is turned off, wow.js is not doing its work.
Turning it on helped.
AOS has no problem with that
hope it'll help someone :)
The text was updated successfully, but these errors were encountered:
If you're using this library along with the Animate.css library while on Windows 11 with the "Animation effects" setting turned off in System Settings, then this is the right and expected behavior.
Animate.css uses the prefers-reduced-motion media query to respect the user's device/system preference for animation effects.
On Windows 11, browsers reflect this preference from the "Animation effects" setting in System Settings.
I hope this explanation helps encourage people to keep using/supporting this brilliant library after reading this issue.
Hello, this is not an issue, i just wanted to share experience :)
I have one old project where I use MDBootstrap and WOW.js.
Suddenly on scroll effects stoped working on some stations - no errors, console log is empty
There is this settings in Windows 11 called "Animation effects". When it is turned off, wow.js is not doing its work.
Turning it on helped.
AOS has no problem with that
hope it'll help someone :)
The text was updated successfully, but these errors were encountered: