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

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

>This gives the same boolean value to 'all' and to 'prefer-reduced', 
which I don't think is good. Did you mean to make 'prefer-reduced' 
falsey as well?

I considered but my train of thought was that falsey means nullish, 
nihilo, no existing. And a reduction means there is most likely 
something left (else it would be called an extinction, disabling, 
etc).

Beyond that nitpicking however, this would work as well:
`motion: all | reduced | prefer-none* | prefer-reduced* | none* (* = 
falsey)`

>@inoas I think the transition period is going to be too long to make 
it practical to have the boolean value oriented the way you suggest, 
and even after the support is universal, authors often think of the 
full fledged design first, and of adaptations later, making the 
"prefer reduce" (no matter what it's called) the better option for a 
naked boolean query.

However as far as I understood you want @media (MG-name) to evaluate 
to false.

I do think it is a non issue if user agents don't support it. It is 
mostly a "nice" feature anyway, as long as it is not about system 
capabilities. It is a feature to be nice to the user and respect his 
preferences. Great stuff, but if it doesn't work (evaluates to false 
because the mq-feature name is not known) the world won't break.

In the context of hybrid web-apps you can most likely know up-front if
 the machine supports the new mq-feature and then design your 
software/css differently knowing about the os/hw capabilities.

BIAS: I am personally in the camp of: HTML and CSS will live a very 
long life and because of that, long term design is much more important
 than short term design. They may be here with us when we walk to our 
graves and maybe even when our children do. Who knows.

People did desktop first and (some/many) are doing mobile first. 
People are doing online-first and they will do offline-first because 
of connectivity and seamless work flows. And people may do 
full-fledged design (colors, contrast, animations) first now... but 
they may (or may not) do accessibility-first. 

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

Received on Wednesday, 7 December 2016 23:46:33 UTC