300ms tap delay removed on Chrome for Android

Re:300ms tap delay removed on Chrome for Android by Pxtl on Friday December 13, 2013 @11:00AM (#6901150)

I still use a WinPhone7 phone and many of these "mobile" sites are completely broken on WP7 IE - they frequenetly have images or boxes that extend outside the bounds of the fixed-width area and don't allow me to zoom out or pan right to see the whole thing.

[ Parent | on HN ]

Re:300ms tap delay removed on Chrome for Android by untog on Friday December 13, 2013 @11:23AM (#6901310)

That's because the Windows Phone 7 browser is unfathomably awful. I say this as a one-time WP7 user and a web developer.

I felt guilty for using it because there was an outside chance it might make someone have to develop for it.

[ Parent | on HN ]

Re:300ms tap delay removed on Chrome for Android by Already__Taken on Friday December 13, 2013 @11:58AM (#6901516)

They changed the browser in the Mango update that's all I know. Came out with the WP8 update.

[ Parent | on HN ]

Re:300ms tap delay removed on Chrome for Android by untog on Friday December 13, 2013 @02:03PM (#6902217)

The WP8 browser is a lot better. WP7 was (IIRC) IE9-level.

[ Parent | on HN ]

Re:300ms tap delay removed on Chrome for Android by sarah2079 on Friday December 13, 2013 @12:06PM (#6901564)

This isn't just your phone. I encounter this specific problem a lot on an iPhone 5 running iOS 6. (And it is just one of the many irritating bugs with mobile sites that I see regularly).

[ Parent | on HN ]

Re:300ms tap delay removed on Chrome for Android by mjolk on Friday December 13, 2013 @11:20AM (#6901292)

That's your phone's fault, not the website's.

[ Parent | on HN ]

Re:300ms tap delay removed on Chrome for Android by zimbatm on Friday December 13, 2013 @11:56AM (#6901500)

Or maybe the site was using tons of -webkit prefixes in their CSS ? You don't know.

[ Parent | on HN ]