A Modest Construct

‘Visual Refresh’

Firefox v2 has reached Release Candidate 1 stage (get it here, by the way), and there’s unfortunately not much to sing about: it still uses the same branch of the GECKO rendering engine as its predecessor, Firefox 1.5. There are some UI improvements, such as the ability to add and remove search engines (a feature I’ve been wanting since 1.0), some slightly reconfigured tabs (each tab now has its own close button, like Opera), and some better in-browser handling of XML. The biggest change trumpeting is built-in spellchecking for text entry fields (right now, it’s telling me that ’spellchecking’ isn’t a word), as well as support for Javascript 1.7, session restore support, and phishing protection.

But what really caught my attention was talking about significantly design changes. In March, I posted an ASCII mockup of proposed interface changes that were uncomfortably exciting. Based on what I’ve seen, very few of those changes ever made it into Firefox 2’s chrome.

The big news was that an outside design firm was working on a visual refresh to spruce up the default theme for Firefox 2 in order to compete with Opera and IE7’s new looks. I really dug what I saw during Firefox’s betas. It wasn’t a dramatic change, but the polish was nice. Instead of big squares around each button, they each had a distinct shape.

Chrome from the beta releases of Firefox 2

But as of the Release Candidate, the theme has changed, and now the toolbar buttons are back to being big square selection areas again, and much larger. The buttons themselves haven’t changed a whole lot, but the way the user interfaces with them has.

Chrome from the release candidate of Firefox 2

Plus, the tabs have gained an ugly ’silver’ gradient that makes them more difficult to read.

Yeah, sure, it all looks nice, but Firefox has to continue to innovate. They aren’t riding the wave of their 1.0 iconoclasm anymore—IE7, despite being a bad browser, is undergoing major changes, especially cosmetically, and the folks at Opera are developing like the wind. Firefox is falling behind, and the decision to be so tepid in the 2.0 release isn’t going to help them any. Come on, guys: innovate!

« Previous post

3 ResponsesLeave one →

  1. It looks abysmal and it was what made me stop using nightlies. At least there’s QuBranch.

    Reply
  2. I’ve found extensions to fix every annoyance I’ve had with Firefox, especially cosmetic ones. Or is your point that they do a better job attracting the layman?

    Reply
  3. I’m sure the beta-era visuals will end up being available as an add-on theme. I just find it aggravating that they’d make the defaults so terribly unattractive.

    Reply

Leave a Reply