Live data from Hacker News

More Responsive Tapping on iOS

webkit.org

31–36 of 36 posts

Re: More Responsive Tapping on iOS

#31
post #20

Earlier quoted context omitted.

I don't even know why this is an option that web sites can control. I should be able to zoom anything I want, site "design" be damned. It actually ruined the iPad experience for me. Early on, when you could pan and resize any part of a page, it was great; then sites suddenly decided they should "help" me scroll, choose the text size, etc. and the iPad screen ended up feeling like a penalty box.

It is important for things like HTML5 games that essentially wouldn't work without this functionality.

I understand "because games" (which are already a horrible abuse of what was initially intended as a way to display hyper-text), but far too often I wander onto some news site or blog that thinks it knows what size text I find most comfortable to read. Honestly, if you're trying to present text in the best way possible, make it easy for readers to choose both font size and column width. This lets readers adjust to suit their visual acuity and reading distance. A lot of sites seem to be designed to prevent both.

Re: More Responsive Tapping on iOS

#32

Standard accessibility disclaimer to people developing websites: please do not set "user-scalable=no" in the viewport meta tag, as this prevents users from pinch-zooming the page. Many designers think "there's no need to allow zooming", but this is often coming from people who are blessed with youth and/or great eye-sight. A lot of people (especially as we get older) need to be able to zoom in to read things, or we j…

I still have 20/20 vision, and I loathe websites that won't let me zoom.

Re: More Responsive Tapping on iOS

#33
post #24

Chrome implemented this ~2 years ago, while retaining the pinch zooming. https://developers.google.com/web/updates/2013/12/300ms-tap-...

If you read the post, WebKit supports fast tap while enabling pinch zooming as well.

Re: More Responsive Tapping on iOS

#34

Standard accessibility disclaimer to people developing websites: please do not set "user-scalable=no" in the viewport meta tag, as this prevents users from pinch-zooming the page. Many designers think "there's no need to allow zooming", but this is often coming from people who are blessed with youth and/or great eye-sight. A lot of people (especially as we get older) need to be able to zoom in to read things, or we j…

What should be the standard disclaimer to all web developers: don't override any defaults. The iOS designers understand everything better than you and every time you disable zooming or change scrolling behavior an angel gets its wings clipped.

Re: More Responsive Tapping on iOS

#36

Earlier quoted context omitted.

The OS-wide accessibiliy zooming is just pixel zooming, though. When I zoom the viewport in a browser, it re-renders the fonts and may even show more detail on the images (assuming the images were sized down to begin with). I also still have the toolbars at the top and bottom of the screen. I agree with you on the triple-finger tap/Ctrl+Scroll options. I use them all the time to check things out, but I still want my…

That's right. A designer who uses `user-scalable: no` is consciously taking that interaction away from you. And in general the result is sub-par, web apps which limit the viewport feel cheap and tacky. It's a useful feature — mainly for apps which render say, an "About" page using a web view but want to make it look like a regular app page.

It's a useful feature that necessitates slower response to taps. One has to pick one or the other.

If you write your css to support dynamic type (in the case of iOS); zooming becomes less valuable as an accessibility feature.

Post reply on HN