Re: [csswg-drafts] No-motion / forced-reduced-motion issue draft (#7440)

@cookiecrook In this case "best solution" is based on not having the granular control in prefers-reduce-motion. If we had to make a call on what prefers-reduce-motion does in these cases, it is better to account for the edge scenarios knowing that will work for those less severe. But we don't have to be so strict. The key is to make the transition feel instant for those who have motion based issues. So instead of a 5 second transition, we do something below half a second. Anything that can happen in under 100ms will feel instantaneous and most likely not affect most motion sensitive users.

-- 
GitHub Notification of comment by nattarnoff
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7440#issuecomment-1428605638 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:07:20 UTC