3 ms·

I don't recall why I've set it up like this, but I'm using the following in an app: <meta name="viewport" content="width=device-width, initial-scale=1.0, maximu

I don't recall why I've set it up like this, but I'm using the following in an app: <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0">. Should the 300ms tap delay be gone in this case too, or is it only apps with precisely <meta name="viewport" content="width=device-width"> OR <meta name="viewport" content="width=device-width, user-scalable=no">?

jaffathecake 13y ago
That removes the 300ms delay in Chrome and Firefox. Although you lose pinch zooming too, which can be a nice usability & accessibility feature.
- eliot_sykes 13y ago
  So to be clear, as long as the content attribute contains "width=device-width", regardless of what comes after it, the 300ms is removed in those browsers?
  - mbrubeck 13y ago
    Firefox currently disables the 300ms delay only if zooming is disabled (either with user-scalable=no or by setting identical min-zoom and max-zoom). We are discussing whether to follow Chromium's lead and also disable double-tap on pages with width=device-width: https://bugzilla.mozilla.org/show_bug.cgi?id=941995 https://bugzilla.mozilla.org/show_bug.cgi?id=941995 (I am a mobile Firefox developer.)
    - kinlan 13y ago
      What would be the convincing factor and how can we share any data/lessons with you?
      - mbrubeck 13y ago
        I think we're already pretty convinced - at least, I am. :) We're just checking to make sure we have consensus; so far I haven't seen any objections.
  - jaffathecake 13y ago
    In the current versions of Chrome & Firefox, the viewport needs to be unzoomable to remove the 300ms delay. However, in Chrome Beta, the 300ms is removed as long as the viewport is <= device-width.