3 ms·

> That's just a stupid choice made by (so many) web developers. Sometimes it's stupid, sometimes not. Disabling zoom removes the 300ms delay added to most inte

> That's just a stupid choice made by (so many) web developers. Sometimes it's stupid, sometimes not. Disabling zoom removes the 300ms delay added to most interactions on mobile devices [1]. You can alternatively use fastclick.js [2] or swiftclick.js [3], but that's an extra lib/http request to load. [1] http://updates.html5rocks.com/2013/12/300ms-tap-delay-gone-away http://updates.html5rocks.com/2013/12/300ms-tap-delay-gone-a... [2] https://github.com/ftlabs/fastclick https://github.com/ftlabs/fastclick [3] https://github.com/tmwagency/swiftclick https://github.com/tmwagency/swiftclick

xyby 12y ago
According to your first link, there is no reason to disable zoom. This gives you the best of both worlds: <meta name="viewport" content="width=device-width"> It retains zoom and gets rid of the 300ms delay. At least in chrome, so the site says. FF says this issue is "RESOLVED FIXED", so maybe they implemented it too: https://bugzilla.mozilla.org/show_bug.cgi?id=941995 https://bugzilla.mozilla.org/show_bug.cgi?id=941995 I have that meta tag on all my sites and I just tested on Android and iOS: Clicking on links and other controls seem instant. And zoom works. Hurray!
- leephillips 12y ago
  "<meta name="viewport" content="width=device-width">" Which is just what I do. Disabling zoom is one of those nonsensical practices that spreads as web "developers" copy code from each other. I suppose there's a use case for it somewhere, but its main purpose is to remove choice and make sites harder to use. EDIT: Actually I also include the initial-scale as in the comment below.
  - Shorel 12y ago
    I have <meta name="viewport" content="width=device-width, initial-scale=1.0">
  - Steuard 12y ago
    Huh. I only have the initial-scale entry, and I think that my sites always show up with page width matching device width as a result. Is there something important that the extra width specification does that I'm missing?
- leeoniya 12y ago
  ah excellent, went ahead and updated my properties :)
wavefunction 12y ago
Disabling zoom prevents people with visual acuity issues from browsing your site. I know only lip-service is paid towards accessibility but zoom shouldn't be able to be disabled except by the user.

xyby 12y ago

According to your first link, there is no reason to disable zoom. This gives you the best of both worlds: <meta name="viewport" content="width=device-width"> It retains zoom and gets rid of the 300ms delay. At least in chrome, so the site says. FF says this issue is "RESOLVED FIXED", so maybe they implemented it too: https://bugzilla.mozilla.org/show_bug.cgi?id=941995 https://bugzilla.mozilla.org/show_bug.cgi?id=941995 I have that meta tag on all my sites and I just tested on Android and iOS: Clicking on links and other controls seem instant. And zoom works. Hurray!

leephillips 12y ago
"<meta name="viewport" content="width=device-width">" Which is just what I do. Disabling zoom is one of those nonsensical practices that spreads as web "developers" copy code from each other. I suppose there's a use case for it somewhere, but its main purpose is to remove choice and make sites harder to use. EDIT: Actually I also include the initial-scale as in the comment below.
- Shorel 12y ago
  I have <meta name="viewport" content="width=device-width, initial-scale=1.0">
- Steuard 12y ago
  Huh. I only have the initial-scale entry, and I think that my sites always show up with page width matching device width as a result. Is there something important that the extra width specification does that I'm missing?
leeoniya 12y ago
ah excellent, went ahead and updated my properties :)

wavefunction 12y ago

Disabling zoom prevents people with visual acuity issues from browsing your site. I know only lip-service is paid towards accessibility but zoom shouldn't be able to be disabled except by the user.