300ms tap delay removed on Chrome for Android

Re:300ms tap delay removed on Chrome for Android by barrkel on Friday December 13, 2013 @10:43AM (#6901047)

Firefox for Android is my primary browser on my Nexus 5 now that the AOSP browser has been removed. On my Nexus 4, I rooted the phone to get back to the AOSP browser, but when KitKat came out, it broke root. I haven't gotten around to re-rooting either phone.

And no, the "view in desktop mode" toggle in Firefox for Android almost never works. I've considered rage-reporting bugs for all the URLs it fails on, but it's an idle fantasy right now. It clearly isn't a priority for Mozilla.

[ Parent | on HN ]

Re:300ms tap delay removed on Chrome for Android by maxerickson on Friday December 13, 2013 @10:50AM (#6901098)

The view in desktop often fails when the site uses a mobile-specific url.

That creates a problem that is hard for the browser to deal with cleanly.

[ Parent | on HN ]

Re:300ms tap delay removed on Chrome for Android by nodata on Friday December 13, 2013 @02:27PM (#6902358)

I haven't seen it fail, but I have only used the desktop view when coming from a page that then gets redirected to a mobile page. Firefox handles that well.

[ Parent | on HN ]