One of the feature that Google Chrome has added to its recent release is the Print Preview feature, which as its name implies, allows you to preview the page before the actual printing. This feature is still in beta and is not available for selection in the Wrench menu yet. For those who are unhappy with the ways that Google Chrome handles your printing, here’s how to enable/disable the Google Chrome’s print preview feature.
On your Google Chrome address bar, type “about:flags” (without the quote) and press Enter.
Scroll down the list until you see the option “Print Preview”. Click the Enable link.
Now restart your Google Chrome. Go to Print option and you will see the print preview.
Similarly, to disable the Print Preview feature, go to “about:flags” and click the Disable link.
One thing to note is that the Print preview feature is still in experimental stage and is not ready for general use. I have tried it on several occasion and it doesn’t load the preview correctly.
In addition, if you are using Linux and often using the print feature to convert webpage to PDF file, then this Print Preview will not work as it doesn’t detect the postscript driver as a printer.
We've spent a lot of time jabbering on and on and on about hardware acceleration in the next generation of Web browsers.
The problem, however, is that no stable browsers have it turned on by default. Unless you're running Firefox 4 beta or Internet Explorer 9 RC, you're probably not enjoying hardware acceleration. Heck, our latest poll shows that almost 50% of Download Squad readers run Chrome, anyway!
Turning hardware acceleration on in Chrome 9, 10 and 11 (stable, beta and canary) is easy, and it can significantly speed up surfing on low-powered devices, like laptops -- or if you're the kind of person who has 30+ tabs open on your desktop PC. We'll show you how to turn on pre-rendering, too, which provides another nice speed boost.
Among the more recent additions is support for background apps, which have actually been part of the Chromium source code for a while now. Unlike the Chrome Apps you may have tried already (like those for Gmail, Docs, and Calendar), background apps can function continuously even though you don't have them open in a tab.
Recently, background app support was added to about:flags. In the current Chromium snapshots (and in the Chrome Dev Channel and Canary), enabling the feature now adds an additional option to your Under the Hood settings -- check the box to enable background apps and run them at startup. Google's choice of "system start" is a nod to Chrome OS, where background apps will likely be the equivalent of system tray apps on your current operating system.
... And don't get your hopes up about that learn more link. Currently, it points to a non-existent page, which isn't surprising considering the Web Store isn't open yet.
Today, the change has landed in Chromium and will no doubt be pushed to Canary shortly. Now called about:flags, the page sports the trefoil (internationally recognized as a warning against radiation) and a bigger, scarier warning. "Please proceed with caution," the intro concludes.
In addition to the name change and new cautionary text, a command line switch has been added to allow users to launch Chrome with all previously-enabled experimental features disabled: --no-experiments. Should you happen to encounter problems browsing after enabling a feature or two, simply add the switch to your launch command and you're back to the stock set of Chrome features.