- From: James Craig via GitHub <sysbot+gh@w3.org>
- Date: Mon, 13 Feb 2023 20:21:15 +0000
- To: public-css-archive@w3.org
The syntax of prefers-reduce-motion was designed to allow more granular control if needed... Future values could be added... Cite: `stop-all` value in https://github.com/w3c/csswg-drafts/issues/5594#issuecomment-724308217 or `forced-no-motion` value in https://github.com/w3c/csswg-drafts/issues/442#issuecomment-265206909 So it still matches the boolean context, but in this case, the implementation can change what's rendered/animated instead of leaving it up to the author. (Note: the "implementation can change what's rendered/animated" is still a hard problem IMO.) -- GitHub Notification of comment by cookiecrook Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7440#issuecomment-1428626176 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 13 February 2023 20:21:16 UTC