Live data from Hacker News

WebKit removes the 350ms click delay for iOS

trac.webkit.org

141–144 of 144 posts

Re: WebKit removes the 350ms click delay for iOS

#141
post #103

Earlier quoted context omitted.

That would be problematic for apps like maps (which I think the street name fonts are too small, and don't scale), or photo/picture programs.

I have bumped into this countless times - street names too small, I subconsciously pinch to zoom, street names get scaled accordingly and are still too small for me. The solution is simple - just move the i closer to my face - but it's thrown me a couple times. Not sure if this is a UX error or just me being daft.

Unfortunately, I'm far sighted, anything closer than about 12-18" from my face tends to be blurry... I know I can/should wear glasses... but really, the phone is the only device I typically have a problem with generally speaking.

Re: WebKit removes the 350ms click delay for iOS

#142
post #71
post #64

Earlier quoted context omitted.

Send GET requests, delay POST. Yes, the whole architecture would need to good undo-support.

A lot of sites out there perform actions on GET requests, though. I just don't see it working out. In any case, once you start delaying things you ruin the original point of getting rid of the click delay - to make things faster!

You only delay non-idempotent actions.

Re: WebKit removes the 350ms click delay for iOS

#143
post #56

As I see it, the 350ms delay was added to support zooming via double-tap. What I don't understand is why double-tap zooming is necessary when we have pinch-to-zoom? Can't zoom via double-tap be sacrificed for instant clicks and everyone is happy?

Seems like you'd still need the 350ms delay (or some amount of delay) for pinch-to-zoom because the two fingers don't touch the screen simultaneously. The sensor reads the first finger's touch and the software has to wait to see if a second finger touch comes in before it decides if the first touch is a tap or the start of a pinch.

Re: WebKit removes the 350ms click delay for iOS

#144
post #139

Earlier quoted context omitted.

As an example of a site that is not good at all on mobile I would cite this very one. In portrait mode the text is way too small to read and zooming in results in text that goes over the edge. In horizontal mode the experience is a bit better but one still needs good eyes to read the comments. Luckily there are enough applications that mitigate the problem.

Bookmarklet to increase font size anyone? Small font size makes it faster to scroll past long threads.

While it works, it is also a hack that very few people know how to use in general my guess would be less than 1%. This site being a huge exception, due to its nature. To scroll past a thread you can collapse it.

As more and more browsing happens on mobile, that should be the new default.

Post reply on HN