You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
That doesn't work in the case of the Wii browser's massive cursor,
though, does it? (It's been too long since I've used a Wii or anything
else with massive ten-foot cursors…)
From this mail thread:
https://lists.w3.org/Archives/Public/www-style/2016Mar/0044.html
@gsnedders said:
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?
@tabatkins said:
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.
Henrik Andersson said:
Not quite. There are hover enabled pens.
@gsnedders said:
That doesn't work in the case of the Wii browser's massive cursor,
though, does it? (It's been too long since I've used a Wii or anything
else with massive ten-foot cursors…)
@tabatkins said:
Do you mean that you think you want the "pop it a little distance
away" for a Wii cursor too? Shouldn't be necessary - it's not that
big.
The text was updated successfully, but these errors were encountered: