- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Thu, 3 Mar 2016 12:06:27 -0800
- To: Henrik Andersson <henke@henke37.cjb.net>
- Cc: Geoffrey Sneddon <me@gsnedders.com>, www-style list <www-style@w3.org>
On Thu, Mar 3, 2016 at 12:04 PM, Henrik Andersson <henke@henke37.cjb.net> wrote: > Tab Atkins Jr. skrev: >> On Thu, Mar 3, 2016 at 5:58 AM, Geoffrey Sneddon <me@gsnedders.com> wrote: >>> One thing that's come up when thinking about design approaches >>> recently is about the necessity to position content such that it isn't >>> obscured when using a touch screen. >>> >>> Imagine a graph which on a desktop shows a label for the current >>> position giving the raw value on hover adjacent to the cursor. Now, on >>> mobile, we can do this using touch events instead of hover. *However*, >>> it doesn't make sense to show the label adjacent to the touch location >>> because it'll be largely obscured by the pointing device. >>> >>> I'm unconvinced it really makes sense to use pointer: coarse for this, >>> though maybe it can be implied that any coarse pointer will obscure >>> content? >> I think you should use "I'm gonna use touch events" as the trigger here. >> >> If you really insist on using MQs as a proxy, tho, it's actually the >> (hover) query you want. If you can't hover, that means you're gonna >> have to poke at the screen with *something* to activate things, and >> that thing will obscure what it's poking at least a little. > > Not quite. There are hover enabled pens. Mm, true. Back to the "use the different style when you use touch events", then. ~TJ
Received on Thursday, 3 March 2016 20:07:16 UTC