Re:Flow browser passes the Acid tests
by dullgiulio on Saturday June 13, 2020 @02:13PM
(#23511383)
Again, disabling features is a feature given to the site developer, not to the visitor, who's actually running the code.
It would be so much better if browsers were User Agents and respected user settings before the will of the site creator.
Re:Flow browser passes the Acid tests
by robin_reala on Saturday June 13, 2020 @03:41PM
(#23512090)
They are? * { animation-play-state: paused !important; transition-duration: 0s !important; }
> Also I don't know how the user would enable it.
In Apple products, it's exposed as an accessibility option:
macOS: https://support.apple.com/guide/mac-help/reduce-screen-motio...
iOS: https://support.apple.com/en-us/HT202655
tvOS: https://support.apple.com/guide/tv/reduce-screen-motion-atvb... (which also disables autoplaying previews!)
Re:Flow browser passes the Acid tests
by robin_reala on Sunday June 14, 2020 @05:13AM
(#23516179)
A friend integrated it into Bootstrap for default animations last year, so I’d guess that a lot of sites are using it.
only for Safari on macOS and iOS
Re:Flow browser passes the Acid tests
by robin_reala on Thursday June 18, 2020 @04:19AM
(#23560953)
Now whether any sites actually make use of it is another matter. Also I don't know how the user would enable it. Perhaps an OS-specific, system-wide setting like dark mode.
https://developer.mozilla.org/en-US/docs/Web/CSS/@media/pref...