Google Chrome dev channel hits v5 in less than two years

For those of you counting, it's been a little over 16 months since version 1 first appeared.
The list of changes so far is fairly small. Mac users will notice a bit more of a difference, with fixes addressing plugin stability and crashing while dragging tabs, a slightly improved cookies manager, and minor tweaks to Chrome's task manager.
On Windows, there are two key updates. First, Chrome will now use your default downloads folder (i.e. Username\Downloads on Vista and Windows 7) instead of creating a new Documents\Downloads folder.

If you're already running the dev channel, just head to the wrench menu -> about and check for updates. If not, you can download the dev channel build manually from this page.













Comments
13
Subscribe to commentsburntcookie90Jan 30th 2010 8:32AM
theme manager would be nice
MikeJan 30th 2010 9:57AM
I also noticed yesterday (and I'm pretty sure this is new) that the extensions icon area is resizable, although the button to pop out the icons when they're not visible doesn't work for me.
FredJan 30th 2010 10:09AM
I am a huge fan of the relocation of the downloads folder. Every time I installed Chrome on a family computer, I had to do this manually. It just never made any sense o have a separate folder.
MichaelJan 30th 2010 10:13AM
I just installed and tested the new dev build briefly, however, I do want to mention this to all those using the current build if any of the new features work.
If so, please do tell! ....and if this is a problem that is only affect me, could anyone assist me in this issue?
- Content Settings reset after clicking close
- The >> button does not reveal any of the hidden extensions
I will post more issues if I find any later today.
sRcJan 30th 2010 12:45PM
okay, using the main downloads folder is nice, that separate downloads folder was annoying (but had the unintended benefit of keeping my Firefox downloads and my Chrome downloads separate, since I use both regularly)
my Chrome is a little confused, though, because it says "5.0.307.1 unknown" as the version right now. started being unknown a little while back, but still downloading devchannel
SamJan 30th 2010 1:36PM
There is an interesting block here, http://blog.chromium.org/2010/01/more-resources-for-developers.html, that talks about a new release of Chrome with some really significant features for developers. Is this article about the same Chrome described in the blog?
Suicidal360FlipJan 30th 2010 2:27PM
That one is talking about version 4 of the stable channel of Chrome.
Sgt ZeppelinJan 30th 2010 3:27PM
In a lot of ways, shouldn't this be more 0.5 than 5.0? Don't get me wrong, I use and love Chrome, I just feel like Google is upping version numbers without a lot to show for it each time.
MxxConJan 30th 2010 6:16PM
this is just the 1st version of what finally will be 5.xx version
Google changes major version number when there are significant comparability changes will happen to the core, for example when Google will make some change to its html engine or javascript engine.
Chrome versions pre 1.0 had V8 javascript engine 0.3 but changed webkit versions.
Chrome version 2.x changed both webkit and v8 engine
Chrome version 3.x changed both webkit and v8 engine
Chrome version 4.x changed v8 engine
Chrome version 5 now has v8 engine 2.0 and will probably change webkit as well.
They are not changing versions just for the hell of it. They have documentation explaining their logic behind major, minor and build version changes.
ProlornJan 31st 2010 1:00AM
Is there a way to determine which Chromium build corresponds to each dev channel release? Or if there isn't an exact match, what the closest one is?
MxxConJan 31st 2010 2:31AM
every single chromium build is a dev channel release 1st.
if it meets all the required parameters it gets upgraded to the beta channel and then upgraded to stable.
ProlornJan 31st 2010 3:51AM
@MxxCon: I don't think you understand. I'm talking about *Chromium*, not *Chrome*. I'm asking which if any of the ~hourly Chromium updates correspond to Chrome dev channel releases.
Money MikeFeb 4th 2010 1:10PM
Unfortunately, the newer builds have removed a very good feature - pinned tabs. There has been a lot of dialog about it (which I've been part of) on the project page, so rather than try to summarize it, I'll just provide this link:
http://code.google.com/p/chromium/issues/detail?id=32845
The one thing I will point out is that there was still one small piece of the feature 'pin tab' left in - drag to pin tab' - in the last few days, but that too has been removed.