Chrome hints and tricks from Ask the Editors

Earlier today, Rafe and I hosted a lively Ask the Editors chat about Google Chrome. As is often the case, we both learned a bit while we were answering your questions. Here's a round-up of some of the more interesting answers.

The secret to many Chrome questions lies behind that wrench icon on the upper right.

(Credit: CNET Networks)

Once you've imported bookmarks, it turns out there is a way to manage them. It's not readily apparent, though. Hit CTRL+B to show and hide the Bookmarks bar. When the bar is showing, at the right end there's a folder icon that you can use to manage those bookmarks.

One reader pointed out that there is a Home button option, although it won't be shown by default. Go to Tools, that's the wrench icon, choose Options and then Show Home Button On Toolbar. The same reader noted that there is no print button, nor a hidden remedy for it. However, the standard Print command that works on every program I can think of also works in Google Chrome. Simple hit CTRL+P and you're good to go.

Another reader complained that his installation of Chrome was running Flash-intensive Web sites at a much higher level of memory usage than in Firefox or Internet Explorer. This struck us as a bit odd, because Chrome imports its Flash engine from the one currently installed in other browsers on your system. However, it might have something to do with the fact that each tab on Chrome functions as its own browser--they're all sandboxed. Keep that in mind, because if you have a lot of tabs running in Chrome you're likely to see memory usage skyrocket.

We didn't bring up the about:memory command specifically, which will show you all memory usage by active browsers on your system, including Chrome. We did talk about about: commands. I erroneously told one questioner that about:config brings up a default advanced configurations list, as it does in Firefox. It doesn't. Other about: commands do work, though, including about:cache to reveal the contents of your cache, about:dns for DNS information, and about:crash which forces the tab to crash.

Chrome may look slick, but it's definitely still in beta. Some of the bugs and hacks we discussed concerned Facebook login failures, scrolling on a Gateway laptop, ad-blocking, and even getting a Google Toolbar in Chrome.

If you have any questions about Chrome that you don't see answered here or in the full chat transcript, feel free to ask away in the comments.

Click here for full coverage of Google Chrome.