The latest from the amazing Aza Raskin, Ubiquity for Firefox is sort of a Quicksilver for your browser. Definitely cool stuff. Visit site »
Firefox 3 gets big kudos for its incorporation of kerning and basic ligatures in the new version of the browser. However, these improvements are negated by the fact that it also enables discretionary ligatures by default, which is likely to destroy the look of pages rendered in certain typefaces. Visit site »
An app that lets you edit CSS and see the results live in both IE and Firefox at the same time. Clever — could be a very useful app.
I presume this is possible because both IE and Firefox have their rendering engines separated from the browser itself and embeddable in other apps (Apple does the same thing with WebKit on the Mac). I said it in Pro CSS Techniques, but I’ll say it again: I really think the separation of browser and rendering engine is one of the single greatest technology advancements in quite a while from the perspective of the web designer/developer. Visit site »
Just recently Jeffrey Zeldman has been bemoaning the sub-standard state of text rendering in Firefox on a Mac. And the sad truth is he only skimmed the surface; Firefox, Safari, Opera and Camino may render even the same font differently. Visit site »
Jon Hicks points out that new versions of Firefox and Camino will use Cairo, a improved graphics library that makes text rendering far, far better than the current Gecko engine — and maybe even better than WebKit. This may just be the thing that finally convinces me to switch to Firefox or Camino full time. Visit site »
Jesse Newland gives a quick overview of what Firebug is all about and how to use it. At our office anyway, Firebug has quickly become the single most important debugging tool in our arsenal. It’s an amazing piece of work. Damn, I wish I didn’t have to switch to Firefox to use it. Visit site »
“Four experts go head-to-head (to-head-to-head) to defend their Web browser of choice in an opinionated free-for-all.” Decent article. I’m still firmly in the Safari camp for everyday browsing, but I often switch to FF when in development mode. Visit site »
I’ve been saying for years that Safari is a better day-today browser for the typical Mac user than Firefox — largely because of it’s glorious text rendering. Nice to see the Z agrees. That having been said, there’s no doubt that Firefox has some available development tools (Firebug, in particular), that makes it a must-have for the web developer. Also, Safari still sucks at Javascript, compared to FF. Visit site »
The next version of Firebug looks absolutely killer. I’m a Safari guy, and I even use Safari as my main web development browser right now — but if there’s one thing that could very well tip me over to Firefox, it’s Firebug. Visit site »
Now featuring close buttons on individual tabs and an integrated spell checker for web forms…which is really exciting, unless you’re a Safari user and have had these features for the past two years. :) Visit site »
As per usual, it’s hard to completely agree with Dvorak, but he definitely makes some interesting observations about how much the choice to build and bundle IE has backfired on Microsoft. Visit site »
Updated to 1.0 with a host of new features and Flock support. This is truly one of the most essential tools for any web designer, I believe. Visit site »
Of these, only one (number three) seems like a valid annoyance. The rest are pretty much completely stupid. Visit site »
They’ll focus on Firefox/Thunderbird/Sunbird etc. As well they should. Visit site »
Congratulations, Jon. Must be quite a thrill to see your work on the cover of one of the best rags out there. Visit site »
As I predicted, the rendering engine and the browser are separating… Visit site »
Hilarious. Visit site »
MS: “Fire-wha? Never heard of it.” Visit site »