Firefox.Opera.Opera Watch posted an interview with Firefox co-founder Blake Ross yesterday, in which he talks about Firefox, Opera, and the relationship between the two. When asked about the rivalry between fans of the browsers, he says, “I think it’s ridiculous. Millions of people out there rely on us to make the Web better, not have pissing contests.” I couldn’t agree more. In fact, I launched The Alternative Browser Alliance primarily in response to that rivalry.

I found it interesting that when asked to describe Opera in three words, Ross’ response was: “Our best ally.”

When web designers switch from focusing on a single browser (usually Internet Explorer) to developing cross-browser sites (usually adding Firefox, sometimes Opera or Safari, ideally all three), they often find that things don’t work as expected in the “new” browser. This can be for a number of reasons, including:

  • Bugs or “missing” features in the new browser (whether incomplete support in the new browser, or proprietary features in the familiar browser).
  • Broken code on the website being handled differently.
  • Different defaults where behavior isn’t well-defined in the specifications.

A big problem is that when you get into the code, a lot of pages aren’t as specific as the authors think they are. When you write code and test it on one browser, you’re not testing that the code is correct, you’re testing that that browser makes the same assumptions you do.

It’s like ordering pizza.

No, really. Let’s say Internet Explorer specializes in Chicago-style pizza, with a thick, chewy crust. And let’s say Firefox specializes in New York-style pizza, with a thin crust. But each can make the other style of pizza on request.

So you call up Internet Explorer and ask for pizza. They deliver you Chicago pizza, and if that’s what you wanted, you figure your order is fine. If you actually wanted New York style, you make sure that next time, you tell them you want that style of pizza.

But let’s say you like Chicago pizza. You get used to calling up IE and just asking for “pizza,” until one day you’re busy, and ask your roommate to order it. He likes to get his pizza from Firefox, so he calls them up, asks for “pizza,” and you get New York style. That’s not what you wanted. Obviously, Firefox pizza is inferior, because they got the order wrong! Well, no, it’s not, and no, they didn’t. They delivered what they were asked for. If you’d told your roommate to ask for Chicago style, Firefox would have been perfectly happy to deliver that style of pizza.

The moral of the story: always be specific with your code. Make sure it’s asking for what you think it’s asking for (validation helps here). And if something doesn’t do what you expect, make sure you didn’t leave that expectation out of your order.

See also: No, Internet Explorer did not handle it properly

(Expanded from a comment I posted at Mozillazine.)

This is good news: Mozilla will be working more closely with various Linux distributors including Red Hat, Novell, Ubuntu, and yes, even Debian, to coordinate Firefox updates, configuration, etc.

There are two main issues: making Mozilla’s Firefox installer work everywhere (it mostly does, but on some systems you need to install some compatibility libraries first), and keeping the distributions’ versions in sync with the official one.

After the Debian IceWeasel debacle, and Fedora deciding to skip Firefox 2 and wait for Firefox 3, it’s good to know that Mozilla has recognized the problem and is working on it. One key piece of information: Red Hat and Novell will both be providing extended support for Firefox 1.5 past its official EOL next April.

(via Fedora Weekly News)

Camino, the Gecko-based web browser designed specifically for Mac OS X, has just released version 1.0… and among the release notes it mentions that it’s a universal binary.

As far as I know, this makes it only the third released web browser to work natively on both PowerPC and Intel Macs, after Safari and Shiira. The Opera 9 previews have been universal binaries, and Firefox plans to have them for their next bugfix/stability release (1.5.0.2, probably sometime next month).

I found a three-year-old blog post by Arve Bersvendsen on web browser zealots that, sadly, is just as true today. Only the names have changed (Phoenix to Firefox).

Seriously, I think these people are hurting the fight for standards….In having to choose whether to believe the Operanians or The Mozillians, I believe J. Random User will believe both. He’ll believe the Opera fans when they say “Phoenix [Firefox] sucks”, and he (or she) will also believe Phoenixers who say “Opera stinks”. And so, J. Random sticks with MSIE.

Arve mentioned his earlier post when he weighed in on the Opera splash page download kerfuffle, which is a great example of why I created the Alternative Browser Alliance. Both Mozilla and Opera have stated goals of promoting choice on the web. Both want to unseat the current dominant browser (i.e. IE). Those goals are better accomplished, if not by outright cooperation, at least by civility. As Arve puts it:

Please, instead of wasting all that time on endless flamewars against the “other browser”, spend your time evangelizing the product you actually use!

Also, a big thanks to Rijk for the shout-out on his blog!

Alternative Browser Alliance