Or as I prefer, Apple Safari Chrome.
If you have any InputManager plugins installed, you’ll probably need to uninstall them to run this. 1Password crashes and PithHelmet screws up the rendering.
Or as I prefer, Apple Safari Chrome.
If you have any InputManager plugins installed, you’ll probably need to uninstall them to run this. 1Password crashes and PithHelmet screws up the rendering.
The new Opera 9.5 Alpha includes performance improvements and a brand new interface for us Mac users.
Still looks ugly.
Safari with Gmail is just one frustration after another, so I moved to Camino and I never thought I’d look back. But now I use Mailplane to access my Gmail e-mail, and there’s no compelling reason for me to stay on Camino anymore, so I thought I’d give Safari another try as my main browser.
Camino is fast, much faster than Firefox, but Safari is still the fastest. In my unscientific and perceived tests, Safari seems to render pages just a fraction of a second faster than Camino, but its the frequency of the lock-ups I get from Camino — especially when I try to open multiple tabs — is my biggest annoyance with it.
Text rendering in Safari has historically been superior to Gecko, but the new 3.0.3 seems to have taken a turn for the worse. Originally, when faced with a typeface that didn’t have a natural italic, it substituted with an appropriate alternative, which is much superior to Firefox and Caminos method of faking the italics by slanting the roman text.
With the new 3.0.3 Safari, they have reversed this decision and are now faking the italic font. In my opinion this doesn’t look anywhere near as nice as replacing the font, but more importantly the slanted roman Lucida Sans is not as legible as using Lucida Grande Italic:
Safari 2.0:

Safari 3.0.3:

The next version of Camino is supposed to use the cairo graphics library, which in turn can use the newer Core Image instead of the current Quickdraw. This gives all Gecko based browsers — including the next version of Camino — a much better “italic font faker”. In general cairo renders text very well indeed, and a more in-depth look is needed once more stable browsers are released — the latest trunk build of Camino renders all italic text as roman, so currently I’m unable to test it.
After using Firefox with Tab Mix Plus and Safari 3.0.3, Camino tabs feel old and tired. You can’t rearrange them, a huge downer for me as I like to organise my tabs into my own little groups, and there’s no way to configure it to open new tabs to the right of the currently open tab, instead of at the far right.
This isn’t to say Safari tabs are perfect, infact without the add-ons mentioned below it would be almost impossible to use Safari. But with the add-ons I much prefer Safari tabs to Camino or Firefox1 especially with the new feature in 3.0.3 where its possible to drag a tab off into a new window.
Unfortunately for Safari it has a lot of quirks that can’t be solved without third-party software. Fortunately though, there are a lot of add-ons for Safari that makes it — in my eye — bringing Safari to a useable state for my browsing method.
I prefer to have everything in one window, sometimes if you click a link in Gmail, it opens in a new window, even if you Command-click the link. With Saft, you can force Safari to open new links and windows in the browser. For me, this makes it worth its $12 price alone.
Safari has no built-in ad-blocking capability, beside using a custom stylesheet. However PithHelmet makes it a much easier process to add your own blocking rules, and the set of included rules block 95% of the adverts I come across. Its a bargain at $10.
SafariStand is the exception in this list of Safari add-ons, being the only free one. But for me it offers little for me except for syntax colouring in the view source window. However this doesn’t work in Safari 3.0.3 even with the beta version of SafariStand thats compatible with it.
For web designing, you can’t beat Firefox with Firebug, this combination of free software has saved me countless hours, although Safari has something similar, they’ve yet to implement live CSS and HTML editing, which is invaluable when you’re working with complex layouts.
But Safari is an incredibly refined browser compared to the oafish Firefox and, certain circumstances, ungainly Camino, and that is why I use it as my main browser.
Everyone seems to be jumping on the beta bandwagon nowadays, and Opera Mini 4 is the latest. I’ve installed it on my phone and have a mini review of it: fan-fucking-tastic.
I’ve been using the new Safari for Windows Beta for a few hours now, and here are my collective thoughts:
Overall a very nice beta that does have it’s fair share of problems. If Apple (or a third party developer) can fix these at the final launch in October, I can see myself switching to Safari on Windows.
Supposedly now Safari is the fastest browser for Windows, effectively killing the Swift project.
The first new Camino build in a while, including many new features was released yesterday.
I’ve been using a specialised build of Firefox for OS X with Aqua widgets for a while now, but even the Intel optimised build is dog slow on my 2.0GHz Core Duo MacBook with 2GB of RAM. After a day of using Camino, it feels infinitely faster than Firefox and the Aqua widgets look more native, although I do wish they added draggable tabs and some of the features in the Tab Mix Plus add—on for Firefox. Hopefully version 2.0 will include support for Firefox add—ons.
It’s now official, Microsoft’s Internet Explorer 7 has gone gold. Currently 49% of my visitors are using IE6, while 19% are using some pre-release version of IE7. Once the balance tips into IE7s favour, I’ll be ditching IE6 support on Ejecutive and fully embracing the wonder that is IE7.
So get upgrading!
I set out for Opacity to have complete browser support across all current platforms with a single stylesheet. However over time it’s become apparent that Internet Explorer is going to need some gentle coaxing of it’s own, in the form of an IE specific stylesheet.
I’m glad that the folks at Microsoft decided to put in conditional comments for Internet Explorer, it’s as if they knew that designers were having trouble with IE’s rendering and needed some hacks.
In any case, heres a list of currently supported browsers:
If you’re on Windows, you have two chances of having a supported browser, two if you’re on OS X, and three if you’re using Linux (assume Safari was replaced by Konqueror).
However over 50% of my current readership is still on Internet Explorer and Windows. I’m not trying to alienate you, I just want you to know what a bitch it is to develop for that browser, and that it’ll take a bit longer for all the kinks to be smoothed out.
Now, lest us not forget in our haste screenreaders. I don’t know how many of my readers use screenreaders (I suspect very few), but designing a site that is read well by screenreaders means designing a site semantically well, which is what every designer should strive for. I consider Opacity to be coded semantically, and most of the pages should be valid XHTML 1.0 Strict. None of that transitional bullshit!
If you do see any errors in the support browser list, do please comment. In fact, if you see errors in any browser please do comment, the more compatability I get the better!
Microsoft has finally decided to stop supporting Internet Explorer for Mac, which hasn’t had any development work on it since 2003. Thats another browser to mark off my support list. Anyone still running Internet Explorer for Mac should follow Microsoft’s advice and “migrate to more recent web browsing technologies such as Apple’s Safari”.