- From: James Craig via GitHub <sysbot+gh@w3.org>
- Date: Tue, 06 Dec 2016 17:34:39 +0000
- To: public-css-archive@w3.org
@nattarnoff wrote: > A complete reduction of non-interaction triggered animation has to be allowed in the settings. Currently, no platforms implement that in native UI or web UI. At such a time that any do, it would be appropriate to standardize in Web API. > Interaction triggered animation needs to be minimized, some stopped depending on what it is. Small animations such as color fades or animated icons on buttons or links likely won't cause a trigger point, but other animations non-essential to the control function may cause problems for users. Reducing motion is good. But stopping/preventing/pausing animation and making the content still readable, actionable, and usable is needed. Herein lies the problem. As CSS and JavaScript-based animations are implemented as primitives, there is no good way for a browser to know which animations may be triggers. Apple has chosen to expose this on its native platforms as a user preference which allows authors to adopt and determine which animations are appropriate to reduce. This takes evangelism, but seems to be working well. -- GitHub Notification of comment by cookiecrook Please view or discuss this issue at https://github.com/w3c/csswg-drafts/pull/586#issuecomment-265216293 using your GitHub account
Received on Tuesday, 6 December 2016 17:34:47 UTC