Maybe someday e-ink will be sufficiently popular for people to demand UIs that work well with it.
The day that happens, I'll figure out how to trick apps into thinking they are running on such a display.
Allow disabling of motion or animation
111–120 of 132 posts
Re: Allow disabling of motion or animation
#112I don't mind animation in general, but I hate smooth scrolling (first thing I disable when installing any browser). There is a trend of adding fake smooth scrolling using js/css, unfortunately.
Counter-point: Smooth scrolling is an essential feature for me. I bought a specific mouse for this because I find sudden line-jumps so disorienting.
My mouse scroll wheel isn't "smooth" so it makes no sense for it to be smooth for me.
> sudden line-jumps
This is definitely something needs to get used to. But the biggest advantage of non-smooth scrolling is that it starts and stops instantly with zero overshoot, which is what I hate of smooth scrolling.
To be more clear, I actually use all three types of scrolling, for different scenarios.
I manually drag scroll bar for finer control, and it has no suden jump issue. I also use auto-scroll (middle click) for super quick scrolling (which is kinda like smooth scrolling).
Re: Allow disabling of motion or animation
#113Earlier quoted context omitted.
The over-scroll stretch animation in Android 12 makes me sick so I had to disable animations completely, as there is no option to just disable that. This does have the effect of making Firefox buggy and not showing the content at the top of a page before you scroll down and up again. Which only works on sites you can scroll on.
I'm happy about the scroll-stretching since it's at least something that happens when scrolling reaches the end rather than just abruptly stopping. My mind head would expect the list to keep scrolling but it just wouldn't without any physical metaphor for why it wouldn't. iOS does this much more nicely.
I prefer the old animation with a grey curve from the button, and I dont really see why it needed to change
Re: Allow disabling of motion or animation
#114I seriously believe this is one of those issues where the browser should enforce the user's preference over what websites want. Rather than try and get every site worldwide to implement this consistently, having the browser disable animations based on the OS-wide configuration would be an easy win for everyone.
It's almost impossible to reliably distinguish animations required for a web site to work properly from animations and changes that can and should be disabled. For example, try to distinguish (from "definitely should be blocked" to "definitely can't be blocked without breaking things"): - An ad mascot hopping up or down telling you to click it - A loading spinner spinning - A progress bar - Information you're waiting…
What it would likely mean is that animations would get stuck in their starting state so you'd see no content. And no one would bother fixing it for the 0.001% of users who turned this setting on so customer support would advise you to turn animations back on.
Re: Allow disabling of motion or animation
#115Earlier quoted context omitted.
I totally get where you're coming from, most employment of CSS animate and transition is excessive and reduces UX. The rule is that you should never have to wait for a UI animation - That said, UI animations done correctly, which are subtle and extremely short, do enhance perception of UI controls state and transitions. But I can't blame people for the broad hate towards animation on the web, so much of it is done po…
I think the best rule of thumb for UI animations is to keep speeding them up until users stop praising the beautiful/elegant animations. They shouldn't notice the animations.
I think iOS does an extremely good job at animations. They help convey movement/what changed/where did I just go, but they are usually so fast and subtle you don't realize there was an animation unless you try hard to spot them.
Re: Allow disabling of motion or animation
#116I don't mind animation in general, but I hate smooth scrolling (first thing I disable when installing any browser). There is a trend of adding fake smooth scrolling using js/css, unfortunately.
Real smooth scrolling where its actually tied to the movement of your finger is very good. Fake smooth scrolling where it's trying to interpolate between scroll events is shit.
I don't know why desktop mice are still stuck in this 80s era of jittery scrolling while trackpads and phones have been scrolling with pixel perfect accuracy for over a decade. And now every product page is tying animations to scroll position which looks great on smooth scroll devices but play as 1fps animations for mice users.
Re: Allow disabling of motion or animation
#117Earlier quoted context omitted.
Counter-point: Smooth scrolling is an essential feature for me. I bought a specific mouse for this because I find sudden line-jumps so disorienting.
My mouse scroll wheel isn't "smooth" so it makes no sense for it to be smooth for me. > sudden line-jumps This is definitely something needs to get used to. But the biggest advantage of non-smooth scrolling is that it starts and stops instantly with zero overshoot, which is what I hate of smooth scrolling. To be more clear, I actually use all three types of scrolling, for different scenarios. I manually drag scroll b…
If you use a trackpad or touchscreen and keep your fingers on, there is no overshoot. This only happens if you move and lift to give it some momentum, or fake JS smooth scrolling.
Re: Allow disabling of motion or animation
#118From my chrome/userContent.css in my Firefox profile directory: @namespace url(http://www.w3.org/1999/xhtml); *, :before, :after { transition: none !important; animation-delay: 0ms !important; animation-duration: 0ms !important; } toolkit.legacyUserProfileCustomizations.stylesheets must be set to true in about:config for this to work. This gives me the best "reduced motion" of all (zero motion), with no effort requir…
toolkit.legacyUserProfileCustomizations.stylesheets must be set to true in about:config for this to work
...the fact that it's called "legacy" is ominous and a sign of things to come. The fact that other browsers have been quite aggressive at slowly destroying any real form of user-controlled customisation is quite telling too. (For exmaple, did you know that IE supported user stylesheets all the way up to its last version, but Edge no longer does? And Chrome removed that functionality over half a decade ago.)
Re: Allow disabling of motion or animation
#119Earlier quoted context omitted.
My mouse scroll wheel isn't "smooth" so it makes no sense for it to be smooth for me. > sudden line-jumps This is definitely something needs to get used to. But the biggest advantage of non-smooth scrolling is that it starts and stops instantly with zero overshoot, which is what I hate of smooth scrolling. To be more clear, I actually use all three types of scrolling, for different scenarios. I manually drag scroll b…
If you use a trackpad or touchscreen and keep your fingers on, there is no overshoot. This only happens if you move and lift to give it some momentum, or fake JS smooth scrolling.
Yeah, I have no problem using "smooth scrolling" when using fingers or touchpad (is there even non-smooth scrolling for these types of inputs?); they pretty much act like dragging scroll bar using your cursor.
I only hate it with mouse wheel.
Re: Allow disabling of motion or animation
#120It's a bit crap that this needs conscious work by developers to implement - I feel like with just a little more thought put into the CSS spec itself, that animations could have defaulted to following the user's OS settings unless the dev explicitly marked them as necessary. Edit: not meaning to absolve developers of thinking about a11y, or to accuse css spec designers of negligence, just making the point that a syste…
unless the dev explicitly marked them as necessary
...which basically all of them will naturally do, because their goals are almost certainly not going to be aligned with yours.