Is anyone else feeling that the Google Chrome developers are desperately trying to raise the version number of the Google Chrome browser to be on pair with Mozilla Firefox and probably Internet Explorer? It is hard to see another reason if you look at the release schedule. The Google Chrome 2.0 Pre-Beta was released less than half a year after the release of version 0.2 of the browser.
The pre-beta release adds several requested features to the web browser. Among the form auto-completion, full page zooms, a middle-click auto scrolling feature, user profiles and Greasemonkey support. The later still has to be activated by launching the Google Chrome browser with the -enable-user-scripts parameters. This is best done using a shortcut.
The release notes for this release contain all changes including interesting ones like the force SSL mode which will only load https sites in the browser. That’s a pretty clever method of getting rid of most phishing related dangers on the Internet.
Check out the instructions on how to download early release versions of the Google Chrome web browser.
Related posts:
- Latest Google Chrome 4 Dev Release Fixes Lots Of Bugs
- Finally: Google Chrome Extensions Turned On By Default In Dev Releases
- Use Google Chrome For Secure Web Browsing
- Google Chrome 3
- Google Chrome Offline Installer
- Google Chrome Adds Greasemonkey Support
- Google Chrome Adblocker
- Google Chrome Session Saver Extension
Great build. Very fast.
Any word on whether SMOOTH SCROLLING is implemented? I simply can’t believe this hasn’t been added to Chrome yet as it is absolutely ESSENTIAL if you READ ON THE INTERNET! I love everything about Chrome so far, but find it difficult to use daily w/o smooth scrolling.
Yes neem you are right. I really miss the smooth scrolling too.
I wanted to upgrade but I read somewhere that you have to delete whole chrome and install it from scratch if you want to have the stable build again. That scared me off a bit, so I will wait for the normal release.
And about the number. Haha, not the developers but the marketing guys give the numbers these days it seems.
So although I can say you are right that they give versions “2″ pretty fast, it is also understandable. Don’t forget that Chrome 2 uses Webkit 528.8, which makes most of the new features possible. So all the new features and the new webkit is not a small step within the development which might justify the cool number 2 ;)
just try
According to my understanding, the final release of Chrome 2 will include extensibility. It’s also running new versions of both the Javascript engine and Webkit. Along with the minor user-interface improvements, I think the use of a new version number is justified — the developer community has been keeping busy!