Google Chrome 8.0.552.210 beta

This was a 25 MB update for me. Not sure why. Reading the SVN revision log takes years and most of the stuff there seems to be about the OS and the Store!

This site just refers you to the SVN log.

One thing I knew was coming was the demotion of click to play from available by default to about:flags.


In edit:Ignore the bit about the 25 MB update. I forgot that I had also updated my AV just before updating Chrome; 25 MB is the sum of the two updates and since it was a single session, I don't have a break-up.

 

any idea why this happened - too many users annoyed by a good security feature?

 

This issue mentions the various other issues behind hiding click to play in about:flags.

http://code.google.com/p/chromium/issues/detail?id=62084

The point about moving it to about:flags is to let the user know that the feature is not 100% ready for mass consumption and that its use could result in anything happening!

 

Click to play has to be one of my favourite features in Chrome. I miss it every time I come home to IE9.

So great to have most of those flash ads just not load at work though.

 

Why do you say "most"?

 

I worded that wrong. I meant most ads, since a lot of ads today are flash. It basically becomes a simple ad blocker in a sense.

 

vasa1, what do you mean by demotion?

I just updated my flash drive to the latest 9.0.576.0 from portableapps and the click to play feature still seems to be fully available. Unless this change is restricted to the 8.x line?

 

it probably is, trunk 9 being the dev/canary line. will be interesting to see whether it makes it into the final, but after this move would not be surprised to see it only in the v9 final

edit - just checked with the biuld 9.0.583 and the feature been moved there too

 

I'm on the Chrome beta track. The first Chrome 8 beta had it on by default. You could go to content settings and it was there. The latest beta doesn't have it there. You have to first go to about:flags, enable it, and then go to content settings to find it there. So the second beta has made it less accessible to the "public". That's what I meant by demotion.

The link to the issue I provided had a lot of other issues (listed on the left hand side) that were to be sorted out before it would be "promoted" again to default status.

If, as you say, the latest dev has got it on by default it would imply that all glitches have been sorted out and that this "default" status will reach 8 beta and eventually 8 stable.

The confusion is sorted out by referring to the release log:

Here, you'll see that dev 587 has it "demoted" whereas the portable apps dev is still 576 (not the latest ).

 

Portable apps doesn't seem to be listing any recent dev right now!?!

 

9.0.576.0 Dev is the latest on portableapps, but vtol appears to have a newer dev version where it's removed.

 

So the point is that dev 576 is older than beta 210 and that's why the demotion is showing in beta 210 and not dev 576.

 

Over at the Chrome help forum there was a post by a Google Employee indicating that Click to play is going to be yanked!!!! It may be brought back later.

Can anyone using the very latest builds confirm that it is absent from about:flags?

 

Beat me to it! Thanks

Just about to try the new dev from PA, is that the "latest" dev build?

edit: click to play is in about:flags of 9.0.597.10 thankfully, I hope they don't remove it.

 

Yes, it's the latest dev but maybe the feature has been removed from the Canary (nightly).

 

I really had to know!

So I installed 10.0.605.0 (Official Build 68547) canary build and it's still there! In about:flags but it's there!

 

Another update of ~24 MB. Mainly security fixes. So what's the big deal about their differential updating mechanism if most of the updates are so huge?

 

9.0.597.19 if it makes any difference to anyone

 

The latest dev has the Crankshaft engine:
The Dev channel has been updated to 10.0.612.1 for Mac, Windows and Linux

This release fixes several crashes as well as:

All
Updated V8 - 3.0.2.1
Updated WebKit - 534.15

But read the comments here since there seems to be some problem with updating: http://googlechromereleases.blogspot.com/2010/12/dev-channel-update_16.html

 

There's a new dev as well:

Google Chrome 10.0.642.2 (Official Build 71689) dev
WebKit 534.16
V8 3.0.7

There's a mention of "pdf files in frames". Their PDF Viewer got a lot of stick from users who were expecting something equal to, or better than, the Adobe Reader plug-in.