Earlier quoted context omitted.
This isn't necessarily a problem as more sites become responsive and make a proper effort to accomodate mobile browsers. Where this will be a problem is poorly written desktop only sites that just make the change to get faster mobile interactions. I hope this encourages more of the former and less of the latter. EDIT: If you don't agree why not explain your point instead of randomly downvoting. I believe this change…
Unscalable != Responsive. One does not preclude the other.
WebKit removes the 350ms click delay for iOS
41–50 of 144 posts
Re: WebKit removes the 350ms click delay for iOS
#42While I do symapthise with those lamenting the lack of pinch-to-zoom, I'm confused: apps don't offer pinch to zoom, so how do you use them? If you can use an app fine without pinch to zoom, you should really be able to use a mobile website fine too. It seems to me that this is an either/or proposition: either you have a not-mobile, pinch-to-zoom-able web site, or you have a mobile-specific site with an app-like viewp…
Re: WebKit removes the 350ms click delay for iOS
#43Earlier quoted context omitted.
As I understand it... If you're using Mobile Safari (or many other mobile browsers), and you double-tap something, it's interpreted as meaning "zoom in to this element". This is useful for pages with narrow columns and things on the sides, etc. However, in order to implement this, when you do a single tap, the browser has to wait to make sure that you don't do a double-tap. So there's a 350ms delay while it's waiting…
Also worth mentioning: Chrome for Android did this last year. GP was asking about iOS, but it's not an iOS-specific thing.
Re: WebKit removes the 350ms click delay for iOS
#44The change applies only to unscalable viewports. That's a shame, because it means some developers will disable pinch-to-zoom to get a faster click response. That makes this yet another unfortunate conflict between usability and accessibility. The older I get, the more I appreciate being able to zoom (I'm viewing this page at 125% on desktop right now).
There are plenty of apps that are guilty of this as well. Instagram comes immediately to mind. Not allowing pinch zoom on pictures I'm viewing on a tiny pocket screen (when there's no good technological reason for it) is a shame. I've turned on assistive zooming on my iPhone to overcome the limitation.
For native apps it's a design choice. For whatever reason (good or bad) they don't want you to zoom in.
For websites instead, pinch to zoom exists for a design deficency, mostly for web pages not optimized for small sized screen. Responsive web design is helping but the gap is not filled yet. Hopefully it's just a matter of time and we'll experience beautiful mobile websites.
For all other needs, there is OS assistive zoom.
Re: WebKit removes the 350ms click delay for iOS
#45Earlier quoted context omitted.
The delay allows webkit to detect a double tap. Otherwise, any element with a click handler would immediately fire, effectively disabling double tapping for their region.
An interesting choice would be to retroactively undo the effects of the single click if a second one was detected.
Re: WebKit removes the 350ms click delay for iOS
#46While I do symapthise with those lamenting the lack of pinch-to-zoom, I'm confused: apps don't offer pinch to zoom, so how do you use them? If you can use an app fine without pinch to zoom, you should really be able to use a mobile website fine too. It seems to me that this is an either/or proposition: either you have a not-mobile, pinch-to-zoom-able web site, or you have a mobile-specific site with an app-like viewp…
Many apps do have pinch to zoom on viewports. Just about any app that displays pictures, for example, or any app that displays large amounts of text.
If you have an area you want to be scalable, you'll have to implement it in JavaScript or use a pre-made component.
Re: WebKit removes the 350ms click delay for iOS
#47Earlier quoted context omitted.
Unscalable != Responsive. One does not preclude the other.
I didn't say it precluded the other, Just that as more sites have a proper mobile view scaling becomes less necessary.
Re: WebKit removes the 350ms click delay for iOS
#48I really don't understand the lamentation around pinch to zoom. There's a fantastic os-level zoom built into ios! Set it up and three-finger-click to activate. And it works great.
Re: WebKit removes the 350ms click delay for iOS
#49How long until this makes it into the Mobile Safari on most people's iOS devices?
Re: WebKit removes the 350ms click delay for iOS
#50Earlier quoted context omitted.
There are plenty of apps that are guilty of this as well. Instagram comes immediately to mind. Not allowing pinch zoom on pictures I'm viewing on a tiny pocket screen (when there's no good technological reason for it) is a shame. I've turned on assistive zooming on my iPhone to overcome the limitation.
> There are plenty of apps that are guilty of this as well. Instagram comes immediately to mind. For native apps it's a design choice. For whatever reason (good or bad) they don't want you to zoom in. For websites instead, pinch to zoom exists for a design deficency, mostly for web pages not optimized for small sized screen. Responsive web design is helping but the gap is not filled yet. Hopefully it's just a matter…
I understand what you mean, but in the context of sites specifically disabling zoom it seems to me that pinch to zoom is a design feature and not a deficiency of traditional web pages. Responsive helps, but there are definitely times when I wish the developers would provide only a desktop view so I can use my browser features to optimize my own user experience. (I am not representative of the general public, I know).