4 ms·

Good on them for listening to prefers-reduced-motion [1]. To the folks complaining about motion, consider configuring your operating system to reduce motion --

by jakear 4y ago

Good on them for listening to prefers-reduced-motion [1]. To the folks complaining about motion, consider configuring your operating system to reduce motion -- make your user agent work for you! [1] https://developer.mozilla.org/en-US/docs/Web/CSS/@media/prefers-reduced-motion https://developer.mozilla.org/en-US/docs/Web/CSS/@media/pref...

verdverm 4y ago
One might also consider reducing animation time. I did this on my android and it made it feel like a new phone again.
- mattlondon 4y ago
  From what I understand of the accessibility issue, reduced motion is about reducing motion, so I don't think that making the motion faster/more visually intense would help those who need the reduced option. I think this is a different thing from people who just want things to feel faster/snappier, vs those who have an accessibility need.
- Groxx 4y ago
  I really like disabling animations on my phone. Everything is so fast, it's amazing. Reminds me that hardware has improved the the past decade. Particularly with Android 12, wow. So many animations added, and they run so, so, so slowly. There were a number of rather severe UI glitches for the first few patches, but it's alright nowadays. Beyond 12's other major issues, that is - I highly recommend not upgrading. Maybe 13 will actually fix some of it.
  - 411111111111111 4y ago
    I switched mine to x0.5 (halved). I wish x0.25 was possible, but that was the lowest option and completely turning it off felt a little janky to me. (If anyone is looking for the option: it's in the developer settings and there are two entries, one for windows and another for general animations.)
  - kbelder 4y ago
    I did that a week ago, just stumbled across the option in the accessibility options. Now I wish I had done it many years ago (is it a new option?). There's not a single animation that is better than its own absence. The worst thing is that it isn't respected by many apps and browsers.
    - Groxx 4y ago
      Yeah, generally speaking many things with "momentum" from a touch will still have momentum (probably a good thing) and anything doing custom animation code will be unaffected (not a good thing! use the framework please, app programmers!). But it does at least get rid of that awful stretch-bounce animation on scroll views basically everywhere. That alone is practically worth it.
mrob 4y ago
Unfortunately, prefers-reduced-motion is fingerprintable even with Javascript disabled: https://news.ycombinator.com/item?id=30237846 https://news.ycombinator.com/item?id=30237846 In addition, "reduced motion" is only a partial solution to the problem of unwanted motion. I would much prefer zero motion. In Firefox, it is possible to disable CSS animations globally, by adding the following to both chrome/userContent.css (with the appropriate namespace header) and chrome/userChrome.css in your profile directory: *, :before, :after { transition: none !important; animation-delay: 0ms !important; animation-duration: 0ms !important; } This also requires setting toolkit.legacyUserProfileCustomizations.stylesheets to true in about:config I have been disabling animation in userContent.css (which affects websites) for years with no problems. More recently, I realized I could also disable it in userChrome.css (which affects the Firefox UI). This exposes what appears to be a race condition bug involving tabs. Occasionally, a tab's close button will stop responding, and that tab will also become impossible to drag to new positions. This can be worked around by attempting to drag a different tab, releasing that drag, then immediately dragging the frozen tab to an empty part of the tab bar, which will unfreeze the tab. I consider this minor annoyance well worth the benefits, which includes disabling animations that would be permitted with prefers-reduced-motion, such as the sliding of the "Find in Page" panel. It is possible that setting an extremely brief animation might avoid the bug without showing visible animation but I have not tested this.

by jakear 4y ago

verdverm 4y ago

One might also consider reducing animation time. I did this on my android and it made it feel like a new phone again.

mattlondon 4y ago
From what I understand of the accessibility issue, reduced motion is about reducing motion, so I don't think that making the motion faster/more visually intense would help those who need the reduced option. I think this is a different thing from people who just want things to feel faster/snappier, vs those who have an accessibility need.
Groxx 4y ago
I really like disabling animations on my phone. Everything is so fast, it's amazing. Reminds me that hardware has improved the the past decade. Particularly with Android 12, wow. So many animations added, and they run so, so, so slowly. There were a number of rather severe UI glitches for the first few patches, but it's alright nowadays. Beyond 12's other major issues, that is - I highly recommend not upgrading. Maybe 13 will actually fix some of it.
- 411111111111111 4y ago
  I switched mine to x0.5 (halved). I wish x0.25 was possible, but that was the lowest option and completely turning it off felt a little janky to me. (If anyone is looking for the option: it's in the developer settings and there are two entries, one for windows and another for general animations.)
- kbelder 4y ago
  I did that a week ago, just stumbled across the option in the accessibility options. Now I wish I had done it many years ago (is it a new option?). There's not a single animation that is better than its own absence. The worst thing is that it isn't respected by many apps and browsers.
  - Groxx 4y ago
    Yeah, generally speaking many things with "momentum" from a touch will still have momentum (probably a good thing) and anything doing custom animation code will be unaffected (not a good thing! use the framework please, app programmers!). But it does at least get rid of that awful stretch-bounce animation on scroll views basically everywhere. That alone is practically worth it.

mrob 4y ago

Unfortunately, prefers-reduced-motion is fingerprintable even with Javascript disabled: https://news.ycombinator.com/item?id=30237846 https://news.ycombinator.com/item?id=30237846 In addition, "reduced motion" is only a partial solution to the problem of unwanted motion. I would much prefer zero motion. In Firefox, it is possible to disable CSS animations globally, by adding the following to both chrome/userContent.css (with the appropriate namespace header) and chrome/userChrome.css in your profile directory: *, :before, :after { transition: none !important; animation-delay: 0ms !important; animation-duration: 0ms !important; } This also requires setting toolkit.legacyUserProfileCustomizations.stylesheets to true in about:config I have been disabling animation in userContent.css (which affects websites) for years with no problems. More recently, I realized I could also disable it in userChrome.css (which affects the Firefox UI). This exposes what appears to be a race condition bug involving tabs. Occasionally, a tab's close button will stop responding, and that tab will also become impossible to drag to new positions. This can be worked around by attempting to drag a different tab, releasing that drag, then immediately dragging the frozen tab to an empty part of the tab bar, which will unfreeze the tab. I consider this minor annoyance well worth the benefits, which includes disabling animations that would be permitted with prefers-reduced-motion, such as the sliding of the "Find in Page" panel. It is possible that setting an extremely brief animation might avoid the bug without showing visible animation but I have not tested this.