Testing out Camino

For the last few days, I’ve been playing with Camino as my default web browser. For my new help system, it has some components that rely on Firefox (for editing knowledgebase articles), so I wanted to give Firefox a try. Unfortunately Firefox doesn’t look like a Mac application. Camino is supposed to be a Mac-ified version of Firefox, so I decided to give it a try. While it’s better than Firefox in terms of being a Mac application, it still has some weird behaviors. It appears to be faster than Safari and seems to be functioning well. I imported my bookmarks and since I’m using 1Passwd for storing passwords to websites, the transition was easy. One bug that is kind of annoying is there are 2 checkboxes for Passwords; “Allow saving in the Keychain” and “Auto fill passwords in web forms”. Unfortunately they don’t work properly. With 1Password, I fill in my passwords with it so I turned off Auto fill passwords in Safari and now Camino. In Safari, the HTTP Authentication passwords still got filled in, but web forms didn’t get filled in. Camino, however, requires that “Auto fill passwords in web forms” be turned on to fill in web forms as well as HTTP Authentication passwords.

I should probably just download the source and fix it, but the last time I touched anything related to Mozilla, it made my head spin and I found some source I had written when I was at Qualcomm that was used without retaining the copyright message (the original source I wrote is still available).

The jury is still out on if I’ll keep using Camino, but the speed and better support for editing in Cerberus and my blog (both use TinyMCE). We’ll see.