For the regular user, Mountain View search engine giant Google this week released Chrome 2.0.172.31, update that fixes a couple of WebKit security vulnerabilities ( details here ). For developers, Google has rolled out Chrome 3.0.187.0 for Windows, Mac OS X and Linux. The Chrome 3.0 update comes with several bug fixes and even a version change to the V8 JavaScript engine, mainly V8 1.2.7.

Please note that Chrome 3.0.187.0 is meant for developers only. You are very well advised to stick with the stable version of Chrome 2.0 if you are a regular user that does not want to get involved with “incomplete, unpredictable and potentially crashing software.” Despite the fact that you might be anxious to try Google Chrome on your Mac OS X or Linux powered machine, downloading the software is not something I would recommend (to the regular user). It isn’t just me, Google itself has recently issued a warning about downloading Chrome for Mac OS X and Linux ( details here ).

Chrome 3.0.187.0 highlights:
- Import passwords from Firefox on Linux-powered machines.
- Use Keychain for passwords on Mac OS X-powered machines.
- Omnibox no longer drops characters when the user types rapidly.
- Web inspector and “--enable-user-scripts” is up and running once more.
- Plugin deadlock does not cause the browser to hang.
- Upon install, extension buttons are now displayed.
- The maximum number of cookies has been increased to 300 (just like in Firefox).
- The first tab is no longer selected when the user clicks an extension toolstrip.
- Better support for Squid proxies.

A complete list of bug fixes and visible changes made in Chrome 3.0.187.0 is available here .

If you would like to get on the Dev channel and get the latest version of Chrome 3.0, just click here .
If you would like to get Chrome 2.0 instead, a download location is available here .