Do people really have this problem? To transition from scrolling to page-turning requires a significant swipe across the pad -- where scrolling would've stopped, and then you'd have started to see the 'go backward' arrow appear across the screen. I find it difficult to accidentally go backward or forward when I'm scrolling horizontally, unless I'm scrolling 'violently' left and right. Is this typical behavior for your app? (such as a user getting to the 'end' on the right, and then wishing to return to the full beginning on the left?)
He's using Chrome (see the screenshot). In my experience Chrome is much quicker to interpret a horizontal scroll as a back/forward gesture; Safari implements a good difference between them (as you describe).
Also, Safari gives progressive feedback on the action and releasing it before halfway cancels the move, whereas Chrome has it instant. IMHO if anything this is a Chrome implementation issue, not a OS X issue.
Don't bash chrome too loudly, you'll be down voted like a monkey with rabies at a kids birthday party.
Dont you know google is every single developers favourite company and they can do no wrong?
It's clearly not googles fault for copying a feature in a half-assed manner, it's apples fault for not predicting that would happen and abandoning the feature.
