#POTD - prague_20.06.2015_7114 by Patrick Lauke
seen from United States
seen from United Kingdom
seen from United States
seen from Germany

seen from United States
seen from Germany
seen from Israel
seen from Spain
seen from United States
seen from Spain

seen from United States
seen from China
seen from United Kingdom
seen from Netherlands
seen from Türkiye
seen from Germany
seen from Türkiye
seen from Türkiye

seen from Türkiye
seen from Türkiye
#POTD - prague_20.06.2015_7114 by Patrick Lauke
On touch devices, a click event has a 300ms delay before firing. The reason for this the delay is that browsers need that buffer to make sure you aren’t going to double-tap on anything. The result is that if you use click events blindly, that delay creates a noticeable lag as users interact with elements on your page.
There has been a Google + post by Rick Byers floating around the last few days claiming the best way to deal with the delay was to eliminate the double-tap zoom altogether. With no double-tap gesture to worry about, browsers no longer need that 300ms buffer and can now fire click events immediately.
...
As Patrick Lauke pointed out on Twitter, this leaves three different solutions for developers, depending on the scenario:
Use something like FastClick, to account for iOS.
Use FastClick or kill scalability (as we’ve just discussed, a bad idea) for Chrome versions 32 and under.
Use width=device-width in their meta tags and celebrate when Chrome 32 and later don’t have a delay.