Do you ever feel some things are missing in Google Chrome? To be honest, I regarded these features for Chrome’s small footprint and the fast V8 javascript engine. Personally, as a web designer, I also like the WebKit engine better than Trident (Of course, the IE one) or the Gecko engine (Mozilla’s one). What else uses WebKit? Apple’s Safari. And the speed is just awesome. Anyways, thanks to Google Operating System for the tips below.
First of all, How do I get the new version?
1. If you don’t have Google Chrome, install it from google.com/chrome
2. Subscribe to the developer preview channel. This is required even if you’ve previously subscribed to the channel.
3. Force the update by opening the “About Google Chrome” dialog.
“The Dev channel is where ideas get tested (and sometimes fail). The Dev channel can be very unstable at times, and new features usually require some manual configuration to be enabled. Still, simply using Dev channel releases is an easy (practically zero-effort) way for anyone to help improve Google Chrome.”
If you don’t like the new version, you can always downgrade to the most recent stable version by reinstalling Chrome.
Google Chrome‘s development is high-paced and version numbers are not very significant, but it’s weird to see a pre-beta release of Chrome 2.0, four months after Chrome 0.2. There are many new things in Chrome 2.0:
Form autocomplete, one of the most obvious missing features from the initial release
Full-page zoom, which resizes images and embedded objects too, not just text. It’s important to know the keyboard shortcuts: Ctrl – to zoom out, Ctrl + to zoom in and Ctrl 0 to go back to the normal view.
Autoscroll by middle-clicking on a page and indicating the direction
Profiles are a great way to separate Chrome’s settings in different categories: you could create a work profile with its own homepage, bookmarks and browsing history and profile for your personal projects. The great thing about Chrome is that you don’t have to close the browser to change your profile: just open a new window in a separate profile.
Support for Greasemonkey scripts (or user-scripts). To enable this experimental feature you need to right-click on Chrome’s shortcut from your desktop, select Properties and add -enable-user-scripts in the Target field. For now, you’ll need to place the scripts in c:\scripts, but the location will change in the next builds.
Other important improvements includes updates to WebKit and the V8 JavaScript engine, a better implementation for SafeBrowsing (malware/phishing protection), new code for the HTTP network protocol.
New to Josh’s Blog? Make sure you follow my RSS feed so you don’t miss anymore great stuff!
