- From: Oren Freiberg <oren.freiberg@microsoft.com>
- Date: Fri, 25 Apr 2014 01:20:22 +0000
- To: "www-style@w3.org" <www-style@w3.org>
- Message-ID: <a42402059d0046e2ab035b465c50a366@BY2PR03MB222.namprd03.prod.outlook.com>
Hey everyone, I have been reading the media queries 4<http://dev.w3.org/csswg/mediaqueries-4/> a bit and I am confused and I am trying to see if my thoughts are aligned with the intention of the spec. For hybrid devices (touch and mouse - laptop or desktop) it is seems matching the least accurate will cause web developer to provide mobile content or mobile optimized content to none mobile devices. Matching both 'fine' and 'coarse' seems like the best way to provide data to web developers to avoid providing mobile content under these conditions. For non-hybrid devices (touch only or mouse only) matching the least accurate makes sense as there is only one choice. My end interpretation is split. On a hybrid device where mouse is the primary input but has added touch as a bonus (desktop with a touch monitor) the UA should either report 'fine' as the touch monitor might not be consider primary source of input or should report both 'fine' and 'coarse'. "If a device has multiple input mechanisms, it is recommended that the UA reports the characteristics of the least capable pointing device of the primary input mechanisms; if there are multiple reasonable "primary" input mechanisms with different characteristics, UAs may make the feature match multiple values." It seems Rick felt we should match both but it looks like Chrome never implemented it. Rick do you still feel the same way and plan on implementing a solution that supports matching both fine and coarse on a hybrid device? http://lists.w3.org/Archives/Public/www-style/2013Apr/0534.html Thanks! Oren
Received on Friday, 25 April 2014 13:25:40 UTC