05 Jun 08 Chrome Keyboard Shortcuts for Chrome Developers

Here’s a couple keyboard shortcuts for helping you to work faster on the Chrome browser:
(I personally find that these shortcuts are great for Chrome developers)

• JavaScript debugger: Alt+`, or select “Page (icon)|Developer|Debug JavaScript”
• JavaScript console: “Page (icon)|Developer|JavaScript console”, or use the Show Console icon at the bottom left of the Element inspector
• Element inspector: Right-click on the page, and select “Inspect Element”. You’ll have to navigate the tree control in the left-hand pane, but you should eventually be able to find the part of the page you’re seeking by watching what gets colored on the page as you hover in the DOM tree.
• Memory tracker: Shift-Esc or “Page (icon)|Developer|Task manager” gets you the dynamic memory, CPU, and Network usage of all currently running Chrome components. Clicking on Stats for Nerds at the bottom left of the Task Manager or browsing to about:memory gets you a snapshot of the memory details of all running Chrome, IE, Firefox, Opera, and Safari instances.
• Create a shortcut: Ctrl-D (like Firefox) or click on the star icon to the left of the address bar
• Rearrange tabs: just drag them where you want them to go
• Add a Home button: “Wrench (icon)|Options|Basics|Home page|Show Home button on the toolbar”

via infoworld Tags:developers, dom tree, dynamic memory, element, firefox, Google Chrome Hacks, hand pane, home button, instances, keyboard shortcuts, left hand, nerds, opera, page icon, safari, snapshot, star icon, tabs, task manager

03 Jun 08 Cool Drag and Drop Tabbing Feature on the Chrome Browser!

Tags:Chrome Features, drag and drop, drop style, firefox, google, new feature, tabs, www youtube

03 Jun 08 Speed Test – Google Chrome versus Firefox and IE!

The guys over at Lifehacker did a nice little test on the 3 different browsers, Google Chrome, Firefox, and IE 8b2.

Above shows that Chrome did load faster when loading 8 tabs.

For CSS, Google Chrome comes out on top due to the fast CSS processing system.  I can agree with this one as I have personally noticed a lot of my sites with heavy CSS files loaded up very fast on the Google Chrome.

In their test, Lifehacker team states that Firefox still beats Chrome in memory consumption but I think it’s hard to compare the memory as Chrome uses multiple processes with smaller memory blocks.  (For example of this, you can refer to this post here.)

In all, Google Chrome is still in its beta stages so time will tell which browser wins the “speed war”.

Do note, however, that Chrome handles tabs differently than others—each tab loads as its own process, so that if it crashes or stalls, the rest of your reading doesn’t go down with it. So if you’ve got solid-state chips to spare, it’s not that much more of a hit to run Chrome in a busy session.

via Lifehacker Tags:beta stages, Chrome Speed Tests, firefox, google, memory blocks, memory consumption, processing system, speed test, tabs