- Site compatibility seems to be fine so far, with a couple of minor issues (see the “Bad” section). Mostly I’ve tested it with a couple of forum sites, LiveJournal, Slashdot, and WordPress.
- I like the simple settings box, with “Basics,” “Minor Tweaks,” and “Under the Hood.”
- It does feel fast.
- Showing the URL of links in the lower left-hand corner is a perfect compromise between the spatial advantages of a permanent status bar and the extra room provided by leaving it out.
- I like the task manager for the browser itself. It’ll be good for developers, but it’ll also be good for users: as the comic points out, if your browser starts chewing up all available resources, you’ll be able to tell what page/plugin/program is at fault instead of just blaming the browser.
- Gears support doesn’t seem to work quite right. WordPress.com doesn’t detect that it’s available. Local WP installs with Bad Behavior can’t sync completely. (It doesn’t send an Accept header on the request for one of the TinyMCE files, which causes Bad Bahavior to think it’s a spambot and triggers a 403.)
- Cookie management is too simplistic. I like to accept all cookies temporarily, but clear everything when I end my browsing session, with exceptions for sites where I want to stay logged in. This is easy in Firefox, a little trickier in Opera, and doesn’t seem to be an option in Chrome.
- I have seen it pause a couple of times, with as few as 5 tabs. [edit: these seem to be related to Flash content]
- I keep hitting the forward-slash key to search within a page, since that’s the shortcut I’m used to in Firefox and Opera.
- The UI does indeed stay out of your way. I guess this sort of makes Chrome the Anti-Flock.
- DNS Pre-Fetching is enabled by default. This is different from full HTTP pre-fetching in that all it does it look up the IP addresses of the links that you might click on. It’s not clear at what point it does this — I don’t remember seeing it mentioned in the comic, which (ironically) isn’t searchable. I suppose it could either hit the domains of all the links on a page, or just those that would trigger HTTP pre-fetching, or even just send the query when you hover over a link (to get a split-second head start before you click). Update Sep. 17: Google has a blog post explaining pre-resolving in detail. Apparently it does check the domains for all the links on the current page.