Re: [csswg-drafts] [mediaqueries] Media Feature: "reduce motion" user setting

While I do think that a positive named feature without any value 
implication in the feature-variable name is the least confusing and 
best to use, this (while perfectly fine on itself) makes it hard to 
use:

> @Mr0grog: because any query using an unrecognized feature evaluates 
to false

If we consider this issue a designer's and browser vendors job, e.g. 
to write the default css declarations WITH motions for quite some 
time, and then use the motion MQ feature just to reduce things FOR 
SOME TIME until there is a broader adoption of the feature name at 
least, then `@media (motion)` makes the most sense IMHO.
Later on media queries like this would both work and make sense, even 
without a value:

```
@media (motion) { } /* declarations for default motions */
@media not (motion) { } /* declarations for no motions */
@media (motion: prefer-reduced) { } /* declarations where users prefer
 little motion */
@media not (motion: reduced) { } /* declarations where the device will
 not reduce motions */
```

### Why?
- Using the motion MQ feature name, we can easily differentiate by 
system capabilities and user preferences. 
- Using the motion MG feature name, we can let the developer/user 
decide if they want to go motion-first or motion-last (like 
mobile-first or desktop-first)

### Suggestion

```
motion: all | reduced | prefer-none* | prefer-reduced | none*  (* = 
falsey)
```

The default value would be `all`

### Animations Off
Animations could be binary-off say for
- conserving battery settings
- epilepsy
- eye-tracking-controls which conflict with animations
- crystalizing readers today
- e-paper of tomorrow
- CPU/GPU power/features (very small socs)

It would be up to the vendor of the device/os if to implement hard (no
 or reduced capability), soft (obligatory or prefered), or both 
settings, for all the different types of motions (zooming, fading, 
smooth/scrolling, bouncing, etc) and if and how to make those settings
 configurable by the end user.


-- 
GitHub Notification of comment by inoas
Please view or discuss this issue at 
https://github.com/w3c/csswg-drafts/issues/442#issuecomment-265434906 
using your GitHub account

Received on Wednesday, 7 December 2016 12:27:40 UTC