Thursday, September 8, 2011

Beta Channel Update

The Beta channel has been updated to 14.0.835.159 for Windows, Mac, Linux, and Chrome Frame.

This release disables chrome:flags.  We are currently investigating some stability issues and are looking to see how greatly flags usage contributes to our stability metrics, hence we are temporarily disabling them.  To see what other changes went into this release check out our change log.

If you find a new issue, please let us know by filing a bug.

Anthony Laforge
Google Chrome

26 comments:

William said...

This is not going to be a popular experiment LOL.

AWood said...

Awesome. No side tabs. Now I need to go back to having tabs the size of a favicon.

jasonvaritekfan said...

So what this means is that Chrome goes back to the dark ages -- no Print Preview. Great!

Why not just add a checkbox to Chrome's settings to turn Print Preview on or off.

This is some bull y'all!

FREEWILLY said...

Good idea. You guys can do whatever you want, as long as you continue to dump millions into this amazing browser and offer it for free! lol...

Besides, half the people reporting crashes have 10 flags enabled and 20 extensions...SMH

norbij├║zer said...

but why not in the dev channel???
why in the more stable beta??

jan said...

whatever helps...

This brings me to a small request: Please enable the "click-to-play" function within the options! I have Chrome pinned to my Taskbar which means I cannot enable the feature via the parameter (--enable-click-to-play)

Neko² said...

Well, I'm switching to dev then ! Can't live without the small url bar :p

NotMikeBrearley said...

Fairly sure that this will result in less crashes. Mainly because without the ability to use plugins (click-to-flash behind a flag), Chrome won't be used at all. Au revoir...

Cody said...

As soon as you make the "New New-Tab Screen" permanent, I'll consider this good news. Until then, bleh

Martin said...

Great idea to disable all "flags" automatically!
You are right, there will be less crashes in beta channel, because everyone using "flags" will switch to dev channel or another browser. :o)
At least until key features like "click to play" are left in "flags".

Only solution I see is:
Temporarily switch to dev channel until flags are enabled again.
And permanently disable auto-update for chrome.

Manual update time to time to verified version is better than being guinea pig for such silly experiments.
I know that beta channel is some kind of testing, but this is too much. I would understand it maybe in dev channel.

Thank you for remembering me that auto-update is large security hole for not verified software.

Chris said...

@jan You can have flags for a pinned icon. Unpin chrome from the taskbar, then open a chrome window with the flag activated (from a shortcut) then pin it to the taskbar. Just don't delete the shortcut you used to open it, so you can use that one that's already in the program menu.

Keith said...

Why don't you just include which flags are being used in your usage statistics, I thought that would of been obvious from the start. I hope the next update brings back flags and is soon. As a non-adblock using Linux user the click-to-play option is almost necessary.

William said...

You can still block Flash, you just have to right click on them, to play.

And it's easy to get to properties from a pinned program....
Right click on pinned program and
then again on the program in the list, you don't need to anything convoluted LOL.

jzero15 said...

I want my flags back :/

Jon said...

I want my flags back as well. You should have only disabled them for those who were providing you feedback.

jan said...
This comment has been removed by the author.
jan said...

@Chris, sort of ~ but I have already figured it out.

If you open the "flag-enabled" Chrome and then "rightclick > Pin to taskbar" on the Chrome icon itself the flag won't be preserved. This was my first try before posting the comment.

Meantime I figured out that after editing the shortcut you have to either "rightclick > Pin to taskbar" on the shortcut or drag&drop it to the taskbar.

Samboc said...

I can understand the need to test new ideas and to let people opt into the beta program with the risk of some bugs being found.

Maybe some form of notification when some major functions are being disabled would be a good idea.

The print preview has been one of the main reasons for going with Chrome.

Any idea how long before functions will be restored or am I better off going back to V13 Stable

Unknown said...

When is the stable version?

spopiel1 said...

Please add back in the Flags!!

DaveyNC said...

I had enabled "click-to-play" because I found that Flash crashed all the time when it started automatically. Sure would be nice to get that feature re-enabled soon.

Vanburen said...

Please enable flags again soon, or at least make click to play a permanent feature outside the flags screen.

LouisL said...

I got a netbook w/ a 10.1" screen: I NEED COMPACT BROWSING

markku said...

Obviously, a lot of chrome users really need click-to-flash. For now I'll be using something else until flags are back in the beta channel!

Freeman said...

This effectively solves the "problem of choice", there's no choice. The next step is to disable all input devices, read-only access should be more than enough, isn't it?

Peter verboom said...

you can enable (--enable-click-to-play) if you have it pinned to the task bar in Windows 7. Right click on your shortcut, then right click on the Google Chrome shortcut and go properties. Put --enable-click-to-play at the end of the target field.