Currently Being ModeratedNov 16, 2012 9:09 AM (in response to James Ward4)
Yeah, criminal. However, I was under the assumption that this was relating to Safari on the Mac. My google search skills failed me and I didn't edit/delete my post before you could catch it and now, it's too late for me to edit it.
Currently Being ModeratedNov 16, 2012 9:18 AM (in response to Alex Zavatone)
Be that as it may (yes you should read the post before replying to it), my response is still the same. It requires pressing specific keys to use the zoom function in Safari in OS X. Don't press those combinations and you will not zoom. Don't use the function, and for all intent and purpose, it isn't there.
Currently Being ModeratedNov 16, 2012 10:33 AM (in response to James Ward4)
That's a pretty ignorant response.
It doesn't matter if I don't press the specific keys.
Using the Macic Mouse as your input device, it can't be turned off, no matter what you set in your trackpad prefs, your mouse prefs, or even by resorting to using terminal commands in the hopes that there is a hidden variable that controls this.
Using the Magic mouse, it is all too easy to trigger some unknown gesture - EVEN IF GESTURES IS TURNED OFF - that makes Safari invoke some action you never intended.
Looking at the source code to Safari's WebKit, certain behaviours are HARDCODED INTO THE SOURCE, if the Mac OS is >= 10.7.
This means the wobbly page views where you can mistakenly tear a page's content away from its border, this means the bouncing, rubber banded scroll view.
These are hardcoded into the source and unless you expect the user to download the WebKit source and build the applicaiton themself, they can not be turned off.
I happen to have spent the money to have three magic mice and Apple doesn't even release OSes that play nice with their own devices. I consider this criminal, since if use another term, this post will be deleted by Apple.
So yes, your post is rather ignorant to the facts at hand. Some of these functions can't be disabled and Apple doesn't seem to care about adhering to the standards they spent 10 years building in their user base, or allowing their users to use the systerm in the manner they have grown used to over the past 10 years (2000 - 2011).
Currently Being ModeratedNov 19, 2012 11:56 AM (in response to James Ward4)
Are you always this sweet? Look. I refuted your claims and you still have issues that someone can have a problem with the way that Lion and Mountain Lion operate.
You are welcome to locate and download the WebKit source, become a registered developer, download and install Xcode, locate the hardcoded values for rubberbandingEnabled and see if you have to check for the properties in an NSView, an NSScrollView, a UIWebView, or whatever is class is using this #define, become an expert on Apple's foundation classes, and disable and then rebuild your own personal copy of WebKit, which essentially is Safari.
You think that this is not an undue burden to the users? You think this is acceptable, when Apple could offered a system level variable of "Mac OS 10.6 style scrolling & web display or Mac OS 10.7+ style scrolling & web display"
Apple could have exposed these properties - it is for NSScrollViewRubberbanding - but it is explicitly ignored in WebKit/Safari/iTunes. They could have offered a nice little GUI setting for it in General Preferences, but they don't and that's simply violating their own established principles, as well as a major annoyance to many users.
But really, you can go ahead and try what I suggested - if you think that's reasonable for a user to have to do to fix the problem.