12 ms·

I'm not sure why you need to wait for potential double taps on clickable elements anyway, couldn't you just have clickable elements not be double tappable?

hmottestad 13y ago
Double tap to zoom is native support.
- emn13 13y ago
  I'm not sure how this matters - can you explain?
  - hmottestad 13y ago
    If you double tap a link on a desktop you will go to that link 'twice'. If you double tap a link on ios you will zoom to that link. Unless you wait for as long as a double tap takes you won't know if the user meant to zoom or to click the link. This is why there is discussion going on about the default view port and user zoomable content.
    - emn13 13y ago
      I get that, but was thrown by your reference to "native" behavior - if you want to be able to double tap a clickable element, you'll need to wait long enough to discriminate the two behaviors. On the other hand - the desktop solution would be fine too; just don't solve the problem (i.e. you can't double-tap clickable content). I think I'd rather have fast responsive taps rather than double-tapping even on links; regardless of the zoomability settings.
marijn 13y ago
Indeed. That's how most desktop browsers handle double-click -- it only happens when the first click wasn't handled (preventDefault-ed). I guess they made this decision for usability reasons (double-tap-to-zoom should always work) but ended up creating a different problem instead.
sp332 13y ago
Sometimes I want to zoom in on a tappable picture. And sometimes the text is so small that I can't aim accurately until I zoom in.
jaffathecake 13y ago
You can actually try this out in Chrome Android Beta. Go to about:flags and enable "Disable tap delay". Here are the problem cases: * Delegated event listeners - as in the click handler is on the html/body element. The listener may do something when a click happens, it may not. This means everything is potentially clickable, and we can't know in advance. * Large click areas - Areas where the article title, summary and picture are all part of the same link. It's not always clear at first, but you'd be surprised how often you trigger it by accident. But give it a go yourself!

hmottestad 13y ago

Double tap to zoom is native support.

emn13 13y ago
I'm not sure how this matters - can you explain?
- hmottestad 13y ago
  If you double tap a link on a desktop you will go to that link 'twice'. If you double tap a link on ios you will zoom to that link. Unless you wait for as long as a double tap takes you won't know if the user meant to zoom or to click the link. This is why there is discussion going on about the default view port and user zoomable content.
  - emn13 13y ago
    I get that, but was thrown by your reference to "native" behavior - if you want to be able to double tap a clickable element, you'll need to wait long enough to discriminate the two behaviors. On the other hand - the desktop solution would be fine too; just don't solve the problem (i.e. you can't double-tap clickable content). I think I'd rather have fast responsive taps rather than double-tapping even on links; regardless of the zoomability settings.

marijn 13y ago

Indeed. That's how most desktop browsers handle double-click -- it only happens when the first click wasn't handled (preventDefault-ed). I guess they made this decision for usability reasons (double-tap-to-zoom should always work) but ended up creating a different problem instead.

sp332 13y ago

Sometimes I want to zoom in on a tappable picture. And sometimes the text is so small that I can't aim accurately until I zoom in.

jaffathecake 13y ago

You can actually try this out in Chrome Android Beta. Go to about:flags and enable "Disable tap delay". Here are the problem cases: * Delegated event listeners - as in the click handler is on the html/body element. The listener may do something when a click happens, it may not. This means everything is potentially clickable, and we can't know in advance. * Large click areas - Areas where the article title, summary and picture are all part of the same link. It's not always clear at first, but you'd be surprised how often you trigger it by accident. But give it a go yourself!