3 ms·
My question: How well will this work on a device like an iPhone where hovering isn't useful. Although I think the the problem with repetitive buttons does need
by jorgem 16y ago
My question: How well will this work on a device like an iPhone where hovering isn't useful.
Although I think the the problem with repetitive buttons does need a solution, I also think it's too hard to assume that users will figure out that hovering over something may allow them to see additional choices.
- coderdude 16y agoI don't think the advice here is suitable for touchscreen devices. In those cases you might consider having a single button that, once clicked, will reveal additional functionality. On another note, it looks as though these guys guys have come up with a way to detect hovering for touchscreens: http://developer.practicalecommerce.com/articles/1900-Maybe-Touchscreens-Won-t-Kill-Hovering-After-All http://developer.practicalecommerce.com/articles/1900-Maybe-... Apparently it can detect the user's finger while actually hover above the surface of the screen.
- calebmpeterson 16y agoThis question crossed my mind too. Anyone have a solution? On the other hand, I just learned the technique of using psuedo-classes early in the css selector chain. Sweet!
- gojomo 16y agoThe solution I've used requires Javascript. It detects when on a touch screen, and if so, adds a CSS class to one default item that gives it the same display-characteristics (including showing hidden controls and shading) as if it were being moused-over. Then, set it so any touch on other eligible elements moves this 'current' class. In some ways, this could be a clearer model for pointer environments, too: reveal the hidden controls on at least one element at the start, and adjust the one full-revealed item as the pointer moves. This requires Javascript, and is a bit more cluttered, but won't leave anyone in the dark about what's possible.