- From: Nat Tarnoff via GitHub <sysbot+gh@w3.org>
- Date: Tue, 06 Dec 2016 17:53:54 +0000
- To: public-css-archive@w3.org
>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. Why couldn't the Web API take the lead instead of waiting for native or web UI? If we establish the ability and best practice, are we not evangelizing that they should catch up and implement it? >there is no good way for a browser to know which animations may be triggers Sadly after thinking through this a little more, I see this problem. Perhaps it is out of scope for this PR, but it is something that should be investigated. On the WCAG side of the fence, there is https://github.com/w3c/wcag21/issues/18 which is about defining accessible animation from interaction. SC 2.2.2 Pause, Stop, Hide covers animation that isn't by direct user interaction. -- GitHub Notification of comment by nattarnoff Please view or discuss this issue at https://github.com/w3c/csswg-drafts/pull/586#issuecomment-265221487 using your GitHub account
Received on Tuesday, 6 December 2016 17:54:01 UTC