March 18, 2008
Apple released Safari 3.1 today for Mac and Windows. For a while now I’ve been using Camino as my main browser. Firefox was a little buggy for me and there are a few things in Safari that bother me enough to not use it all the time. I have been paying close attention to Safari development. They have been talking up these speed enhancements and support of a lot of new standards.
Reasons I haven’t used Safari:
Double-click on the tab bar does not open a new tab. This now works in 3.1! It may sound like a small nuisance but it really drove me nuts. I’ve become so used to it in my other browsers. Now that this is fixed it brings me a lot closer to using Safari.
Open In Tabs – I keep most of my tabs on the Bookmarks Bar. I have a bunch of folders and even subfolders inside of those. When I click Open in Tabs it opens all the bookmarks at that level but also all the bookmarks in the subfolders. This is not how Firefox got me used to the Open in Tabs functionality. I like having the level of organization and still open a bunch of pages at once, I just want them to be the pages in that folder. Apparently it was changed to this behavior in Safari 1.3, here is the Apple Doc.
New windows are created instead of tabs. Please just give me the option to go all in on tabs.
After opening a folder in Bookmarks Bar hovering over a different folder does not open it. Too crazy? I’ve gotten used to this not working because Camino doesn’t do it. Firefox does. It really took me a while to get used to. It’d be nice to have, but I can live without it.
WordPress support. Usually Safari would screw up any post I tried to make in WordPress. This is the first one I’m trying with 3.1. (Update: It still removes all line-breaks. Not sure whose fault this is, I guess we’ll find out when WordPress 2.5 comes out soon.)
I am very happy with the double-click for new tab functionality but without fixing the Open in Tabs I can’t use Safari all the time. I know there are some add-ons, so if anyone knows of one that will support this please let me know. I’m not thrilled about that, but I’d give it a shot. The WebKit engine behind the scenes is great, I’d just like to be able to use it without going crazy.
I have similar nitpicks with iChat which have led me to avoid using that as well. I’ll cover that later.