I couldn't have said it better myself, Alex. I've been in the same boat as you, been in unnamed projects to make Lion better, etc.
I'm glad that Lion is there for people who like it. And I'm glad Snow Leopard is still around for those, like me, who prefer it. Snow Leopard is superior to Lion in every way that matters to me and that's why I stay with it.
Right. And I came here looking for technical assistance. Unfortunately, there is apparently none available to fix this particular issue. Which is too bad, but it is still helpful to have this site to let me know not to bang my head trying to figure out a way to disable "bouncy" scrolling.
I really, really hate it. Seriously, it makes me ill, from motion sickness. And it annoys me to no end that I paid to upgrade to Lion, and in the process have downgraded my browsing experience. My solution is switch to non-Safari browsing, which is too bad, cause I was otherwise very happy w/ Safari. Is that a rant? I guess so. But if I hadn't come here and seen the link that you and others posted, I wouldn't have easily found a place to direct my complaint so that Apple will see it...
At the end of the day, this is about a community of Mac users helping each other. Swapping complaints is part of that communal experience, and will (hopefully) help lead to solutions. Telling someone with a legitimate issue to go join a Facebook group is about as antithetical to the idea of community as you get!
I did. I'm kinda attached to my wireless mouse, if you know what I mean....
I've got a buddy who works as an software engineer at Apple - I'm gonna email him and see if there is anything he can do about getting an "opt out" feature added. I'm sure some folks don't mind it, but it drives me NUTS. Seems like an off switch wouldn't be too hard to add....
And there's no way to avoid the rubber band effect if you're using the macbook trackpad.
For those who don't have friends inside Apple, you can request Apple to allow a "opt out" feature by sending feedback:
The reason it irritates me so much is because it's pretending to be more realistic, more physics-enginesque, but the bounce is completely unrealistic. Nothing that bounces in the real world does a single bounce, and then stops precisely at the end without subsequent bounces.
Because the physics of Apple's bounce is unrealistic, it breaks user expectations, which is a big booboo in UX.
Who cares? I hate it.
I want my scrolling to STOP at the end, not bounce around when I'm on my computer.
It's like the iOS views that allow you to drag the content away from the window it is in and then watch it bounce back. I have NO use for this. And I certainly don't want it in Safari.
What ***** is that this "bounces" is a property that is able to be set in code when you are creating your app. Apple could, very easily offer a GUI switch of "Enable scroll bouncing" and "Enable view bouncing" but they don't.
It's in the code for the scrollBars and the the scrollViews. These are in EVERY LION APP. (also iOS)
There is a variable called bounces and methods to enable and disable it. If I had more time, I'd look them up and post them. Ahh, screw it.
On iOS, it's UIScrollView. Should be similar in the Mac OS. Either NSScrollView or iOS ScrollView. OMG. I hate their comment: 'Bouncing visually indicates that scrolling has reached an edge of the content." NO YOU IDIOTS! Reaching the END of the scroll region indicates that that scrolling has reached the end of the content.
With the ubiquity of these methods and variable It's simply IDIOTIC (and insulting to the way they have thought us to use the OS for the past 12 years) that Apple didn't simply offer us switch to use the approach that we prefer.
Properties and methods:
A Boolean value that controls whether the scroll view bounces past the edge of content and back again.@property(nonatomic) BOOL bounces
If the value of this property is
YES, the scroll view bounces when it encounters a boundary of the content. Bouncing visually indicates that scrolling has reached an edge of the content. If the value is
NO, scrolling stops immediately at the content boundary without bouncing. The default value is
- Available in iOS 2.0 and later.