Unfortunately you are confusing everybody (well me anyway) by saying 5.0.355.0

There's nothing on the blog to say Beta is at the same level !!

Thank you Google Chrome for the fast update
Now its 5.0.355.1 and working

No it's not !!!!

It's 5.0.335.1

Anyway, intrigued by your results I decided to investigate further ...

Basically the reason it originally said 5.0.335.0 Beta (when no such Beta existed) was because you installed it incorrectly ...

In actual fact, if you had then gone on to install the Stable version (because of your frustrations with the drag crash) you would have got 5.0.335.0 , at which point you would have noticed that something was obviously wrong ...

The reason for all this confusion is because you didn't uninstall the installed version of Chrome before you installed the Beta version ...

Hidden away on the Chrome Channel Changer is a little note about changing channels, basically if you are going to an earlier release you need to uninstall the existing installation of Chrome first...

The current version of your Chrome is held in the Local State file in your Used Data folder, I'm guessing the Channel ID is held somewhere else and the two are pulled together on the 'About Screen' ...

The reason for holding the two separately (I suggest) would be to discern between versions having the same number, but on different channels (as often happens with the Stable and Beta channels)...

You probably didn't notice, but the installation process was not exactly the same as it is when you install to a clean (ie No Chrome) system, it went straight from the 'installing Chrome' to 'Thank you for installing Chrome' ...

It didn't present you with the Import bookmarks and shortcut options ...

By the way this isn't hyperthetical, I actually installed both the Beta and Stable versions without first uninstalling my Dev version of Chrome ...

So, somewhere along the line, the installation gets out of 'sync' the channel ID (or whatever) gets updated but the version number doesn't, but what is true is that you are still on the Dev channel !!

The problem is with Google, they should check when installing Chrome that there are no current versions installed, especially if it is a previous version !!!

Oh btw with reference to the 'duh' in your post; have to be honest I instinctively use Ctrl and + when I can't read something on a web site, guess I should take more notice of whether it's part of the page or something embedded !!

Anyway, thanks for stimulating the old grey matter ;-)

I'm sorry

@mg2

Nothing to be sorry for ...

Plus, it was the sort of problem/issue I thoroughly enjoy investigating and resolving ;-)

Anyway, glad your 'Drag' problem is sorted, if only they'd get their collective a**** into gear over 'tab pinning'...

One thing I've learnt about being on the Dev channel, if it's a 'major' (liked this drag issue) then they get it fixed PDQ ...

If it's change in functionality and/or direction you just have to hang on and see what comes out of it ...

@ StevePaul:

I LOVE the auto updating of my Chrome, these good people at Google can take care in a speedy way of any "glitches" without me having a headache each time...

@Luc

Auto update isn't that bad these days, but in days gone by (long, long time ago) it was an absolute nightmare !!!

Tbh it's not the occasional 'glitch or crash' that bothers me, it's more when they suddenly change or remove a 'feature', 'pinned tabs' being a prime example ...

PS:

It's a shame you can't get them to auto update your signature while they're at it ;-)

"It's a shame you can't get them to auto update your signature while they're at it ;-)"

Good one !!!! haha

PS: Done...

@Luc

That's why I don't bother anymore ...