2009-12-08
A short list of Chrome issues (beta 1)
… most of which are actually due to me being stuck liking the way Safari does things, or a consequence of it being a beta.
- You can’t invert open behind - on Safari command shift click opens in a new window behind the current one with command click opening in a new window in front/focus, whereas Chrome is hard-wired to do the opposite (and with tabs to boot)
- Tab moves between all link and form elements, not just form elements. (I can’t remember if Safari picks this up from the system-level preferences or not, but it does what I want, and Chrome doesn’t.)
- There are no command key shortcuts to open bookmarks in the toolbar¹
- The combined text/title/URL completion in the “Omnibox” means you have to go too far into a URL to easily work around the lack of command key shortcuts
- You can’t set a default font size, so sites that honour relative fonts (like delicious, and (in places) Twitter) now have Huge Idiot Typefaces
- While Chrome sensibly uses the keychain (so, like Camino, it can share usernames and passwords set up in Safari) it doesn’t offer to complete the username part, meaning more typing.²
It’s been a nice evening, but despite being rock solid, Chrome goes back in the “for emergency use” box for a while. Sadly, given the team’s approach to customisation, it might be quite a long while indeed.
¹ Camino also gets this wrong, in a very odd (yet explicable) way: if the bookmark bar is visible, it works, but if it’s not, it doesn’t. The developers seem to believe that an invisible option is confusing. I believe that twenty vertical pixels on a laptop display are more precious than feedback. Sorry.
² Probably this is sensible from a security point of view but it’s annoying me, so I’m listing it anyway. I’m sure you’re sensible enough to make your own decision.
