Earlier quoted context omitted.
What if it sends an AJAX request? You can't exactly undo them. The browser JS environment is sufficiently complex that "just undo"ing something seems like it would be... complex.
Send GET requests, delay POST. Yes, the whole architecture would need to good undo-support.
WebKit removes the 350ms click delay for iOS
121–130 of 144 posts
Re: WebKit removes the 350ms click delay for iOS
#122Earlier quoted context omitted.
I couldn't disagree more. There should always be a way to make the content I'm looking at bigger in order to see it more clearly, especially for users with poor eyesight. "responsive design" does not magically eliminate this need, and I agree with the posters saying that disabling of user-scrolling should never have even been allowed in the first place. And that's not even touching on the fact that most "responsive"…
You can't zoom in normal apps.
Re: WebKit removes the 350ms click delay for iOS
#123Earlier quoted context omitted.
I couldn't disagree more. There should always be a way to make the content I'm looking at bigger in order to see it more clearly, especially for users with poor eyesight. "responsive design" does not magically eliminate this need, and I agree with the posters saying that disabling of user-scrolling should never have even been allowed in the first place. And that's not even touching on the fact that most "responsive"…
You can't zoom in normal apps.
Re: WebKit removes the 350ms click delay for iOS
#124Earlier quoted context omitted.
You on the other hand are making the assumption that developers are capable of making that decision informed and "correctly".
Well... Yeah. What's your point? That Apple knows better about the content and performance characteristics of my app than me?
(Yes, there's accessibility zoom, but I didn't know about that until this thread)
Re: WebKit removes the 350ms click delay for iOS
#125Earlier quoted context omitted.
Oh God, thank you. You've restored the mobile web for me. I can't stand the stupid "responsive" design crap. There shouldn't be any way to disable user zooming on mobile. Web developers simply can't be trusted.
Responsive is good, however dictatorial coding isn't. No reason responsive ought not be user friendly as well. The problem is that many devs seem to thing that they know best for their users. However a larger number don't actually understand that their vision of how a web page should operate isn't necessarily how a web page should operate. Too many cooks trying to be chefs. I admit that I don't have an expert grasp o…
I'll disagree. Responsive is a cop-out -- reminds me of the "mobile" versions of websites. Give me the full version, and stop messing with the layout and experience between the web and the phone.
Re: WebKit removes the 350ms click delay for iOS
#126Earlier quoted context omitted.
I didn't say it precluded the other, Just that as more sites have a proper mobile view scaling becomes less necessary.
The more sites attempt "proper mobile views" the worse it gets. In 2011, mobile safari was practically perfect. Now half the sites I visit have found some way to dick things up because they hired some nitwit designer to "mobile first" things to shit.
Those "mobile special" layouts are annoying enough on their own on a phone (with their dumbing down of the UI), but they are doubly annoying when you're used to the web version of a website, and have to hunt for things in the "responsive" mobile version.
Re: WebKit removes the 350ms click delay for iOS
#127Will removing this 350ms delay really make user feel faster response?
Re: WebKit removes the 350ms click delay for iOS
#128Earlier quoted context omitted.
Responsive is good, however dictatorial coding isn't. No reason responsive ought not be user friendly as well. The problem is that many devs seem to thing that they know best for their users. However a larger number don't actually understand that their vision of how a web page should operate isn't necessarily how a web page should operate. Too many cooks trying to be chefs. I admit that I don't have an expert grasp o…
> Responsive is good I'll disagree. Responsive is a cop-out -- reminds me of the "mobile" versions of websites. Give me the full version, and stop messing with the layout and experience between the web and the phone.
Also, responsive design does not mean disabling zoom at all.
Re: WebKit removes the 350ms click delay for iOS
#129Earlier quoted context omitted.
> Responsive is good I'll disagree. Responsive is a cop-out -- reminds me of the "mobile" versions of websites. Give me the full version, and stop messing with the layout and experience between the web and the phone.
But the full versions of the sites are often horrible for mobile. It is as simple as optimisation for vertical vs horizontal layout. Also, responsive design does not mean disabling zoom at all.
I've never found that to be the case. Or if I did, it was far less often than being annoyed with the lacking, scaled down, "horizontally enhanced" mobile layout.
Re: WebKit removes the 350ms click delay for iOS
#130Earlier quoted context omitted.
While I agree with what you are saying I have a minor nit: "For websites instead, pinch to zoom exists for a design deficency, mostly for web pages not optimized for small sized screen." 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…
Non-zooming sites can (and should) honour your system-wide font-size setting, giving you the ability to use the system's settings to achieve uniformly comfortable reading experiences across websites and apps. Zooming doesn't do much to give users much control over the reading experience -- iOS does not let users set or change the viewport size, so everyone gets the same columns to zoom into/out of. If you want text b…