Hacker News Reader

Comment by tajen | Hacker News Reader

It is a problem. And you know the worst? There are "mobile" libraries like Zapto (=jQuery) which enable touch features at the expense of zooming. I didn't check the details, but the sheer idea of blocking zooming on a mobile device is plain stupid.

View on HN

This frustrates me as well. The problem is that some interactions aren't possible or performant if zooming is allowed.

Why is that the case?

Many mobile browsers have a ~300ms mobile touch delay unless you disable zooming (because they wait to see if it's a double-tap zoom event). iOS is the biggest issue with this now, as I think Chrome on android better listens to some new directives to not wait

I think with iOS, even if you disable zooming, you still get that 300ms delay. A better solution would be to instead of listening to only click, listen to both click and doing interesting things with ontouchend. I recall implementing something like that a while ago, where when an element is touched (ontouchstart), I saved the X and Y coords of the touch, and when the user releases their finger (ontouchend), if the finger hasn't moved more than say 32 pixels, I fired the callback to whatever. Of course, you also need to do something to prevent triggering the event twice, but when done correctly, you get both nice quick click events and zooming.

Yep, I think there's a well-known library (or 5) around for this somewhere.

edit: https://github.com/ftlabs/fastclick

As someone who is visually impaired, I care more about being able to READ the site than I do about nice scrolling.

I mean, I like nice scrolling / etc., please have it, but being about to read the content is a prerequisite.

Zepto?

Reply on news.ycombinator.com