As the search giant has recently released the Beta version of Google Chrome 17, it’s no wonder that the 18th version is already available as the Dev build.
Tagged as 18.0.1003.1, Google Chrome 18 Alpha is mostly bug fixes so far. Excluding those, there are also few minor improvements worth noting.
From now on, Google Chrome will reject weak RSA and DSA keys when validating certificate chains for HTTPS and do a better job at error handing in audio wave out.
Although this is just the first of many v18 builds that are yet to come, judging by the size of changelog, it looks like Google is gearing up for quite a release.
Google Chrome 18 Alpha (Dev) Changelog
- Updated V8 – 22.214.171.124
- Fixed several crashes
- When a profile is synced, use GAIA name + GAIA photo for avatar – Use Google OAuth userinfo API to get profile information
- Added support for manifest_version attribute for extensions
- Eliminate drawing glitch on WebUI radio controls
- Fixed regression with extension omnibox API where whitespace would get trimmed
- Fix page zoom for plug-in documents
- Fix race condition in extension service that causes extensions installed
- Folders in the wrench menu and application menu are greyed out
- Better error handling in audio wave out
- Made URL filter for web request API mandatory
- Reject weak RSA and DSA keys when validating certificate chains for HTTPS; related UI
For a complete list of fixes, see the following post.
Update: starting from build 18.0.1010.0, Google Chrome 18 also includes ability to “Rotate Clockwise” and “Rotate Counterclockwise” when viewing PDF documents.
Out of curiosity, how many of you are using dev builds?
About (Author Profile)
Vygantas is a former web designer whose projects are used by companies such as AMD, NVIDIA and departed Westood Studios. Being passionate about software, Vygantas began his journalism career back in 2007 when he founded FavBrowser.com. Having said that, he is also an adrenaline junkie who enjoys good books, fitness activities and Forex trading.