I think I’ve found a group of people just as annoying as elitist Mac users. This group would be the no-holds-barred Firefox/Mozilla zealots who hang out at Spread Firefox and post Diggbait articles about the state of browser compatibility. Yes, Firefox has done great things for Web standards and interoperability of sites; it’s also nice to have the same browsing UI on Windows, OS X and Linux boxes. Yes, not everyone at Spread Firefox is drooling with glee as they report sites for misplacing a LI tag. Unfortunately, today’s target of my wrath does not meet the criteria for exemption.
It’s specifically this list that irks me today, written by a guy whose interests apparently include bashing “Micro$oft”, South Park boot screens, and writing about browser incompatibilities.
The only reason I even bring this up (and since I refuse to go into the Digg comments; they’re already at over 110 and I don’t think I’ve seen one intelligent one yet) is because Nathan links to blackberry.com as one of the sites that’s incompatible with Firefox.
Wait, hold up. blackberry.com (the consumer/promotion site for the devices) is about one of the most likely sites to comply with Web standards, since it’s also designed to be viewable on a BlackBerry device. What’s this guy on about? His complaint is specifically the Google Talk instant messenger download page:
http://www.blackberry.com/GoogleTalk/index.do Uses obsolete ActiveX junk. And Google is somehow involved with this?!?
For reference, here’s what the website says when I go to it using Firefox:
Notice
Microsoft Internet Explorer 5.0 or above is required to download this Instant Messenger.
This web page uses ActiveX controls that work only in Microsoft Internet Explorer. To ensure that Google Talk for BlackBerry devices is correctly downloaded to your BlackBerry, this site is not designed to work with any other Internet browsers.
This page is a separate application with an ActiveX control, designed to connect to your device using USB and load a Java MIDlet (which can’t be done with conventional web scripting language, so ActiveX is really the only way to go.) Furthermore, anybody accessing this page can also do it from their BlackBerry device, which also properly loads the application without the IE requirement.
For the record, I use both IE7 and Firefox at work, each for about 50% of typical usage. All my custom development works equally well in both browsers, except for SharePoint/Project Server integrated plugins (and that’s a Microsoft limitation.) Yes, it’s not entirely great that you can’t load MIDlets with Firefox, but the reality of the business world is such that you can count on a Windows/IE combination for corporate desktops; a Firefox extension/plugin for the same functionality doesn’t really make sense when there’s already a browser-agnostic way of performing this task.