Dec 13 AT 5:06 PM Dima Aryeh 7 Comments

Chrome Beta 32 no longer features a 300ms tap delay on mobile sites


Mobile web browsers incorporate a delay between your tap and something happening, 300ms in the case of Chrome for Android. This is to allow the device to wait for the second tap, so you can double tap to zoom. Without this delay, the instant response would make double tap unusable. Thus, the delay is necessary.

But on mobile sites, where you are unable to zoom anyway, the delay is cumbersome and unnecessary. Thus, in version 32 of Chrome Beta, Google has removed the 300ms delay on mobile pages that do not support zooming. Regular pages will be unaffected by this change.

Google Chrome will have the same feature implemented when it reaches build 32, and other browsers might follow suit. It’ll really make your phone seem a lot faster, like shown in the video. Go download Chrome beta and try it for yourself!


Source: Android Police

Dima Aryeh is a Russian obsessed with all things tech. He does photography, is an avid phone modder (who uses an AT&T Galaxy Note II), a heavy gamer (both PC and 360), and an aspiring home mechanic. He is also an avid fan of music, especially power metal.

    Most Tweeted This Week

  • Jess Blanchard

    Assuming 30 mobile site clicks per day, we’ll save 54.75 minutes per year. 54.75 minutes. 42 toothpicks. Kmart sucks. Uh oh. Fart.

  • Ryan

    Any site that doesn’t support zooming, mobile or desktop, can kiss my a$$. I hate when I either can’t read the text in an image or the font is just too small and I can’t zoom. Why does zoom ever need to be disabled?

    • Brandon

      “Thus, in version 32 of Chrome Beta, Google has removed the 300ms delay
      ***on mobile pages that do not support zooming***.”

      Reading comprehension ftw.

  • aranea


  • donger


  • สามารถ แสงแก้ว


  • eman

    I use Chrome Beta and am now aware of this feature. Guess I’ll go try it out for myself.