- From: Oren Freiberg <oren.freiberg@microsoft.com>
- Date: Fri, 25 Apr 2014 23:50:11 +0000
- To: Tab Atkins Jr. <jackalmage@gmail.com>
- CC: Rick Byers <rbyers@chromium.org>, François REMY <francois.remy.dev@outlook.com>, CSS WG <www-style@w3.org>
>The fact that all the keyword MQs have mutually exclusive values so far isn't thus a necessary aspect, just an >incidental one. I always assumed this was intentional very interesting!! Although it is incidental I think it has become the way developers think about it and to me it doesn’t seem like this is the right place to break from that mental model. >We also thought of this but rejected it. Using a special value for "both" means that anyone who designs a >stylesheet for "course" or "fine" will *not* match this value. I think that is the expectation that "course" or "fine" will not match the combined value. I think this is desired more than a burden from my perspective. >Sure, it's possible for people to have styles for both "(pointer: >coarse)" and "(pointer: fine)" that fight, but I think most of the time the styles'll work fine, and letting people >naively apply their (pointer: coarse)" styles on a "hybrid" device will be fine. I expect "coarse" content and "fine" content to be very different so naively applying both won't be okay. I would guess that mobile devices (tablet and phone) to be the majority of devices with only "(pointer:coarse)" so I expect their styles to be very different from devices with only "(pointer:fine)" typical desktop computers. As hybrid devices are not as prevalent it makes me feel that they will end up with bad experiences or more bugs due to accidental clashes.
Received on Friday, 25 April 2014 23:50:44 UTC