Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Trinatek

macrumors newbie
Original poster
Jul 20, 2011
26
0
Minnesota, USA
I guess I'm not completely aware of how the release cycles have worked out in the past and though I realize the Dev channel for Google Chrome has been receiving a steady flow of updates, the OCD in me just needs a "stable" release.

Any ideas, clues, guesses?
 
I recently switched back to Safari (the two finger Back/Forward is a lot cleaner + double tap to zoom is nice on an 11in), but I was using the most recent Dev build of Chrome (14.0.835.29). It supports two finger Back/Forward and I didn't really have any problems with it.
 
Hm.. so should I go for the Developer's build or Canary then I wonder? Also, is there any way to sync all the different releases (stable, dev & canary) in terms of favorites, passwords, history, etc. ?
 
Hm.. so should I go for the Developer's build or Canary then I wonder? Also, is there any way to sync all the different releases (stable, dev & canary) in terms of favorites, passwords, history, etc. ?

Yes the normal sync works for all. Also Canary runs beside public Chrome, it doesn't replace it.
 
I have been running Google Chrome on Lion and have had zero problems.
+1

It's not really that I'm afraid I'll run into problems using Chrome, it just sucks that (from what I last heard) a lot of Lion's features and gestures aren't incorporated into Chrome quite yet.

Safari's performance sucks, but you have to admit that the transitions and smooth-nature of the browser is pretty aesthetically pleasing.
 
Perhaps, I should have surrounded stable with quotes in the thread title: "stable"

The point of this thread was never meant to question how stability of Chrome as a browser, but was aimed more-so at the various builds & release channels and the lack of Lion-specific support in the "stable" build.
 
Perhaps, I should have surrounded stable with quotes in the thread title: "stable"

The point of this thread was never meant to question how stability of Chrome as a browser, but was aimed more-so at the various builds & release channels and the lack of Lion-specific support in the "stable" build.

Only thing I find Chrome lacking is the page foward/backwards swipe feature.
 
For those that want to use the standard Chrome release, but would also like the two finger swipe forward/back gesture functionality:

Download "Better Touch Tool" (free): http://www.boastr.de/

You can setup system wide or application specific gestures for all of Apple's touch devices. Bind the forward (Cmd+Right Arrow) and back (Cmd+Left Arrow) keyboard shortcuts to the two finger swipe right and left gestures respectively.
 
I had the error 12 issue a week or two ago. I had just started using Chrome again after not using it for several months. I tried deleting the app, reinstalling, and even switching which build I was using, all to no avail. I finally had to remove the app and remove every file I could find that was part of the app (I think there was the plist file, application support stuff, etc..) Once I did that and then reinstalled, the error disappeared and it updates correctly again.
 
I had the error 12 issue a week or two ago. I had just started using Chrome again after not using it for several months. I tried deleting the app, reinstalling, and even switching which build I was using, all to no avail. I finally had to remove the app and remove every file I could find that was part of the app (I think there was the plist file, application support stuff, etc..) Once I did that and then reinstalled, the error disappeared and it updates correctly again.

To assist with "fully" removing an application and related files, try the free program AppCleaner: http://www.freemacsoft.net/
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.