We think the spec should avoid ambiguities around non-pointer devices---we were bitten by this during our implementation. Details: Even though 'pointer', 'any-pointer', 'hover' and 'any-hover' values are meant for pointing devices only (right?), the spec http://dev.w3.org/csswg/mediaqueries-4/#mf-interaction defines 'pointer' and 'hover' values ambiguously with respect to inclusion/exclusion of non-pointing input device like keyboards: A. The 'pointer' value definitions include non-pointing devices, but the 'hover' value definitions don't. These defs use "... primary input mechanism ..." and "... primary pointing system ..." respectively. B. The 'any-pointer' and 'any-hover' definitions include non-pointing devices: "... capabilities of all the input devices ...". Hope we didn't miss anything in-between. Mustaq On Thu, Dec 18, 2014 at 1:54 PM, Florian Rivoal <florian@rivoal.net> wrote: > > > On 15 Dec 2014, at 21:54, Mustaq Ahmed <mustaq@google.com> wrote: > > Update: we are on track to ship 'any-pointer' and 'any-hover' media > queries in Chrome M41 ( > https://www.chromestatus.com/features/6460705494532096). These are > already available in Chrome canary builds for testing. Note that we shipped > 'pointer' and 'hover' media queries in M38. > > BTW, IE 11 tech preview is also shipping these: > > https://status.modern.ie/mediaquerieslevel4interactionmediafeaturespointerandhover?term=media%20queries > > > Good to hear, thanks for the update. Any feedback on the feature itself, > or the way it is specified, based on this implementation? > > Also, I suppose you wrote some tests in the process of developing this. It > would be greatly appreciated if you could contribute these to W3C to be > included in the test suite for media queries 4, to help move the spec along > the REC track. > > - Florian > > PS: Hi Microsoft, same questions about feedback and tests for you. > > > > > >Received on Thursday, 22 January 2015 13:47:15 UTC
This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:50 UTC