(No comment was entered for this change.)

(No comment was entered for this change.)

(No comment was entered for this change.)

Now that the Lion’s out of the bag, these are safe to open up to the world.

 Issue 87252  has been merged into this issue.

In the newest build swiping back with one finger by default. The two finger swipe is an option, but it will result in not being able switching desktops with the two finger swipe.

Swiping right means going a page back, swiping left will take you a page further.

	Screen Shot 2011-06-26 at 12.55.13 PM.png 253 KB   View   Download

That's particular to the mouse.  Trackpads still use the gestures described in the original post.  However, those gestures are tuneable, just as they are for the mouse.

Is there anyway to currently get around this issue without using Safari? Even using an application to use custom gestures (BetterTouchTool), Chrome still will not page back/forward with either 2 or 3 fingers on the trackpad.

I am currently using Better Touch Tool and setup 2 custom guestures for 2 finger left & right for chrome only

2 finger left -   keyboard shortcut "cmd["
2 finger right - keyboard shortcut "cmd]"

here is a link to the chrome keyboard shortcuts in case you cannot understand what i have above
http://goo.gl/1RCCs

also you will have to swipe a little longer than what you are use to for it to register

	Screen Shot 2011-07-06 at 11.31.50 AM.png 135 KB   View   Download

In the GM you can tune some of the gestures. Set the "Swipe between pages" gesture to "Swipe with two or three fingers"

Going back/forward is now working in Chrome!

	Screen Shot 2011-07-07 at 11.53.41.png 12.8 KB   View   Download

That's not a good solution.  Wouldn't that make it impossible to swipe between spaces with three fingers (the default)?

Chromium should obey the "Swipe between pages" setting, like Safari does.

Yes markjaquith Chrome should obey the "Swipe beween pages" setting but it doesn't by default, that is the whole point of this bug being filled.

The "Swipe between pages" setting only works if you switch it to "Two or Three Finger" setting instead of the default of "Two Finger" setting.

So Chrome still needs to be fixed so that way it will work with the default setting of "Two Finger" swipe.

Also ddelong you can still swipe between spaces because when you change the "Swipe between pages" setting it automatically changes the switching between spaces setting to use Four Finger Swipe.

I have this exact issue as well.

Not for nothing, I suppose, but I actually prefer to have Chrome/Safari (OS X Lion by default, therefore) to swipe between pages on two or three finger swipe. And then, use four finger swipe to swipe between full screen apps. To some degree, that is how iOS 5 behaves on the iPad with multitouch gestures, and that unifies the interface for Apple users. So, I think this is an Apple problem with defaults. Perhaps Chrome should support either option via a preference, or just follow the system preferences as Safari does.

It should respect the system preferences.  If you want two finger swiping, you can configure it there.

It's counterintuitive to a user for Chrome not to respect that system preference, and to behave in a different manner to Safari.  Right now, Chrome is broken for me and I won't be going back from Safari until I can use my gestures!

Same here! I miss the 2 finger back but for some reason its not enough to make me go back to safari. I hope they fix this soon!

Switching to "2 or 3 fingers" crashes chrome for me. It has since the earlier DP's.

same here: Chrome 13.0.782.55 crashes (!) on Lion GM when I try a "2 or 3 fingers" swipe.

I'm also running Chrome 13.0.782.55 on the Lion GM. 
But the change of gesture doesn't make Chrome crash on my machine.

If you'd please go to chrome://crashes and paste your crash IDs here that'd be helpful. Alternatively, you can attach the Apple .crash report files (but please attach the whole report rather than pasting it here).

Fresh from the crash:

http://pastebin.com/bAXeKBRZ

best, Ralf

Chrome 12.0.742.122 crashes on my computer as well when I'm using 2 or 3 fingers gestures

I also get crashes from swiping to go back / forward on Lion. My machine is configured to use three fingers for that gesture. The crash id is 2e207c00f8905abb.

The crash reports all implicate net.wonderboots.MultiClutchInputManager. I don’t know what that is, but I found http://osx.iusethis.com/app/multiclutchinputmanager. Doesn’t seem to have been updated since 2008, well before Lion was a gleam in Steve’s eyes.

Those who are affected by this crash, can you try disabling or bypassing that?

@bridgey re: comment 24:

That crash is inside something called MultiClutchInputManager, which I think is this: http://wcrawford.org/2008/02/28/everytime-i-think-about-you-i-touch-my-cell/. If you (or anyone else on this bug) has it installed, please uninstall it and see if the crashes keep happening.

multiclutch was INDEED the culprit. Found it in HD>Library>InputManagers folder, deleted.

Need to restart Chrome and swiping should work again.

yep, success here, too: using AppDelete to get rid of multiclutch did the trick. THX!

Not sure that we've gotten acknowledgement about the root problem here though.  Does everyone agree that Chrome should honor the Mac OS X Lion setting for swipe between pages?  I think that is the correct solution.  That way, people can configure the operating system the way they want and ALL their apps including Chrome honor them.  

I just want to make that point since the crashes that some people experienced really have little to do with the root issue logged here.

I agree completely.  Currently I have to reconfigure my gestures to 3-finger swipe in order to properly move forward/backward in Chrome.  This shouldn't be the case (and most users won't know to do this anyways).  Chrome should honor the OS's forward/backward settings whatever they may be.

I think we should stay on focus with that issue here.

Even to ask whether you should be respecting the OS X preferences is kind of missing the point: You don't really have a choice if you want Chrome to work.

For example, if you decide that you want to keep the three-fingered back gesture for Chrome, you will have problems, as the three-fingered back gesture is now used to switch between spaces & full-screen apps. If you were to succeed in intercepting a three-fingered swipe, you would go back, but the browser would disappear as the OS switched to a different space. 

Apple added new gesture-tracking abilities and new gestures to support functionality like LaunchPad and Control Center. If you use something other than what the OS preference states, you will be in conflict with another gesture.

It just simply won't work for Chrome to have its own gestures that differ from the system-wide settings. This is a basic part of the OS X philosophy: there's a clean, well-documented standard for the UI, and your app will be broken if you try to deviate from it.

There's another wrinkle to this, which is that the default here is not actually a two-fingered swipe. It's a two-fingered scroll. The correct behavior for the default is to do a turning-the-page animation like switching between screens on an iPhone. Also, to go back, you scroll right, like you are going back in a book.

So to really support this correctly, there is probably new code that needs to be written, or new APIs that need to be hooked up.

But at the minimum, you need to make sure that you can respect all three OS X Lion settings for back & forward. For now, Chrome just doesn't support the trackpad in Lion except for vertical scrolling. This is a big problem since trackpads are now the primary input mechanism for OS X.

(I'm a little surprised that this wasn't addressed before Lion came out. It's a major incompatibility and I know several people who got Lion today & switched to Safari until Chrome & Firefox are fixed. Yes there's a workaround, but it requires changing several of the default gesture settings, which makes them pretty inconsistent.)

Has to be 2 firngers

And just 1 finger for the "magic mouse", right?

press alt + 3 finger swipe left or right and you can go back and forward again (workaround)

Hi All
Just solve the problem.
For trackpad, change "swipe between pages to 3 fingers" and "swipe between full-screen apps to 4 fingers",
and now, you can use 3 fingers swipe left and right to go back and forward :> cheers

But for magic mouse, I have no idea how to get it back

Lots of complaints about this coming in from the forum as well. See example thread below:
http://www.google.com/support/forum/p/Chrome/thread?tid=36701a9aeca0d08c&hl=en

I just went and got a Magic Trackpad. I'm going to see what I can do about this today.

(No comment was entered for this change.)

I agree, Chrome should use System Preferences setting for swipes and should provide the same experience as Safari.

Also, a 'Tap to Smart Zoom' might be a good addition.
Thanks.

No need for "I agree" posts. It's clear what needs to be done here (chrome should support the system defaults on 10.7).

(No comment was entered for this change.)

 Issue 90118  has been merged into this issue.

I added gesture support for the two-finger swiping if it's enabled via System Preferences. This will be in Chrome 14 for the next dev and canary channel builds.

Bugroid, where'd you go?
----------------------------
[Mac] Add two-finger gesture support for Lion, which respects the system preference.

BUG=78676
TEST=With two-finger gestures enabled, swipe left/right with two fingers. Page goes back/forward.

Review URL: http://codereview.chromium.org/7488023

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=93720

 Issue 90623  has been merged into this issue.

Thanks for the quick turnaround, Robert!

There's a complaint (from this TechCrunch article) that the fix for this issue in Chrome 14 Dev has the swiping gestures in reverse from what Safari has. It looks like Lion reversed the direction of the gestures also. In other words, swiping right in Safari with 2 fingers navigates to the previous page, while in Chrome you have to swipe left to do the same thing. 

Is this the case? 

jtan: that is (was)  issue 90342 . It's fixed in the canary.

Oh great. Sorry I missed that. Thanks thakis!

 Issue 89979  has been merged into this issue.

(No comment was entered for this change.)

 Issue 91810  has been merged into this issue.