Shadowmaster’s Blog - Web browsers

Firefox is dead, long live Firefox

nospam@example.com (shadowmaster) — Thu, 28 Jul 2011 18:35:00 +0000

It’s not entirely unexpected for me, but it’s the kind of news one hopes to never find in his front door, like a car-bomb if you will. If this goes ahead I can imagine that less and less time and human and economic resources will be spent on the Mozilla Firefox proper for the PC, once B2G catches the OEMs’ attention.

I guess it’s time for me to accept (again) that Firefox has ultimately become the open-source Internet Explorer.

Firefox 6 beta

nospam@example.com (shadowmaster) — Fri, 08 Jul 2011 22:55:00 +0000

And here it is, at last. Just like the last time, the new version migrates from Aurora to Beta on Tuesday but it isn’t offered via the update channels until the next Friday, while the newer ex-Nightly is published in Aurora in the meantime.

I still think this is unnecessarily awkward for users who are interested in one specific Firefox version, or who want to avoid disabling incompatible add-ons as much as possible.

Firefox 7 in Aurora channel, however...

nospam@example.com (shadowmaster) — Thu, 07 Jul 2011 22:56:00 +0000

… Where’s Firefox 6 beta?

Supposedly, Firefox 6 entered the beta channel on July 5, yet there’s no signs of it in the Mozilla FTP server or in the website proper.

With Firefox 7 entering Aurora now, I’m in a slightly uncomfortable position because I hoped to continue tracking version 6 once it moved to beta — now I’m using an old version 6 snapshot from Aurora hoping that the beta will be packaged and announced soon.

It seems somewhat inconsistent from my standpoint to let Aurora be replaced by a newer version before the previous Aurora is properly promoted to Beta.

Interestingly, the same situation appears to have occurred with the announcement of Firefox 5 beta in May, the difference being that I didn’t particularly mind because it was in preparation for the first official release after Firefox 4 and the decision to switch to a rapid release schedule, so a little schedule slip was to be expected for an initial deployment.

Firefox 5

nospam@example.com (shadowmaster) — Wed, 22 Jun 2011 04:11:00 +0000

The announcement that Mozilla was switching to a “rapid” release cycle did not entirely catch me by surprise back in the day. With the advent of Google Chrome to rekindle the fire of the Browser Wars a couple of years ago and its significant contribution to the general adoption of HTML5, I knew Mozilla Firefox 4.0 would have little to offer that wasn’t already the standard in Chrome.

Now that version numbers are meaningless for Firefox users, Mozilla refers to their latest milestone simply as new version.

It’s kind of sad to see those who were once pioneers in open-source web technologies development — in no small part thanks to Microsoft Internet Explorer and the death of the formerly glorious Netscape Navigator — now relegated to following in the footsteps of the youngest actor in the market, an actor which really just took Apple’s Webkit library as a building foundation and released the resultant project under one (if not the one) of the most recognizable brands of the Internet.

As far as I understand the roadmap for Firefox 6 and 7, there’s very little in terms of user-visible features ahead this year, and most improvements are either bug-fixes (like in good old point releases), HTML5 crap or minor polishing. That is not to say that I don’t welcome any performance improvements, but I think that the Mozilla folks need to come up with something really new and unique if they don’t want to see their market share drop to dangerous levels and lose the war to Google’s over-pretentious product.

Choosing an email client with Firefox

nospam@example.com (shadowmaster) — Sun, 22 May 2011 22:57:00 +0000

Whatever rules Mozilla Firefox follows to determine the user’s default email client don’t seem to work properly on Debian, at least not when GNOME is not the desktop environment originally installed. For whatever reason, what Firefox tries to do with mailto links and the Send Link context menu option is to open the Evolution mail client, which is not installed with the KDE or LXDE desktop environments.

Fixing this is supposed to be trivial, and it is, but the relevant option is hidden in the worst possible place in Preferences.

Chromium/Google Chrome does not have a user-accessible setting for this, but somehow still appears to get the right idea from the desktop environment.

Cats, rainbows, and stars, oh my

nospam@example.com (shadowmaster) — Mon, 18 Apr 2011 20:10:00 +0000

I don’t know what’s the worst (or best) part: that HTML 5 is being used for this kind of gimmicks, or the fact that there’s people who are entertained by a gray cat who shits rainbows while flying- er, running across the universe with a pop tart glued to its back. Does that make sense? No. Does it need to make sense? No — this is the Internet, after all.

Feel free to click the links, but don’t blame me if your score in future IQ tests drops by a significant amount as a consequence.

Protip: nyan.cat works best with Google Chrome. Firefox 4 and Opera 11.10 miss the rainbow animation for some reason, on Linux at least. Not that I care, really.

Firefox 4 gets a clue, plus Bonus Track

nospam@example.com (shadowmaster) — Sat, 16 Apr 2011 06:08:00 +0000

Apparently the people at Mozilla finally decided to give their last Firefox release a try on a Linux/Gtk+ configuration other than Ubuntu 10.10’s default, or some diligent user reported to them how awful the new interface looks to the rest of the world who’s not using Windows. In any case, I seem to be receiving new builds through their beta channel, and a few hours ago I got my hands on Firefox 4.0.1 “beta” build 1, whatever that means.

The following picture should speak by itself: (Hint: look between the Firefox button and the toolbar.)

Before switching to Mozilla Firefox 4’s builds from the Nightly (Minefield) channel some time around mid-2010, I used to follow closely the blog of one of the Debian Iceweasel maintainers, from which I got goodness such as updates on the status of Iceweasel 3.6 for Debian Sid/Squeeze in Experimental, that I used for a while.

There’s a little piece of customization advice for Iceweasel/Firefox 4.0 users posted around January that I overlooked until now.

Turns out that this night after Firefox 4.0.1’s update, I decided that the “Firefox button” should match the Oxygen window decoration in style — because I’m that crazy. I took the ~/.mozilla/firefox/<session>/chrome/userChrome.css modifications from the blog post and played around with various combinations until I produced something marginally uniquer.

#appmenu-toolbar-button > .toolbarbutton-text {
  /* oxygen "carved" effect */
  text-shadow: 0px 1px 0px white;
  /* bold */
  font-weight: bold;
}

I am actually afraid of messing around with the many possibilities of XUL/CSS styling further, lest I spend the rest of the month producing my own full-fledged Firefox theme. The fact that I can handle CSS makes this all the more worrisome.

Web browsers and UI design divergence

nospam@example.com (shadowmaster) — Thu, 07 Apr 2011 04:26:42 +0000

Web browsers break any established GUI design molds and this is no news for us. It was a necessity to create new controls (also known as widgets) in the ’90s when the Web was still a new, unknown thing and no common consensus on how users should interact with it existed. However, with time this practice has lost some of its technical grounds to become more of a profitable marketing strategy used by giants such as Mozilla and Microsoft to create distinct looks for their products.

Above we can see four browsers I personally consider major players in the GNU/Linux ecosystem in particular. From left to right, top to bottom in descending order of wheel reinvention and UI differentiation, we have: Opera 11 (???), Google Chrome 10 (GTK+), Mozilla Firefox 4.0 (XUL/GTK+) and Konqueror (KDE/Qt4) from KDE SC 4.4.

At the lower end, we have Konqueror, which has been designed to blend in with its parent application suite, the KDE desktop environment, so it uses a common visual design instead of inventing its own. At the top there’s Opera, a cross-platform browser that is not part of any specific suite and attempts to keep a consistent internal look between different operating systems, resulting in various reimplemented controls with different, custom functionality and a visual design unique to this software product.

In the middle we have Google Chrome and Mozilla Firefox, which have chosen to use the GTK+ toolkit to avoid reimplementing too much and concentrate on their actual business, that is, web browsing. But something’s horribly off about these two.

In Google Chrome’s case, we have a default, “Classic” theme that presents the user with the distinctive Chromium look and feel but keeps the standard GTK+ application design for modal dialogs. Embedded input controls in web pages such as checkboxes and unstyled command buttons appear to be rendered by a custom engine using Chrome’s own ideas of what a widget should look like. As Chrome belongs in the GTK+ territory like all of the GNOME desktop environment, this makes it really stand out as an individual application that behaves and looks like nothing native to GNOME or other GTK+-based environments. As an alternative, we can choose to use the “GTK+ theme” in the application’s preferences, which does nothing but switch the color scheme to respect the user’s desktop preferences a bit and fallback to GTK+’s icon paths for some (not all!) toolbar buttons.

This so-called “GTK+ theme” keeps the hideous low-contrast, Chrome-style scrollbar in the web page view area as well, basically mocking users who would hope for some desktop consistency and accessibility by choosing this option.

Mozilla Firefox provides an interesting case. Powered by the XULRunner framework, it aims to blend in with every one of its target platforms, using native Windows controls on Windows and GTK+ as a backend on Linux. However, someone didn’t get the memo with the main window’s tab bar, and instead of native GTK+ versions we get awful customized tabs that do not respect the user’s chosen GTK+ engine. It seems that in Firefox 4’s particular case the developers intended to achieve something closer to Opera in design, which worked in Windows, but didn’t get completed for Linux — probably due to time constraints and lack of volunteers to do the grunt work required in the coding area. Firefox 4 in Linux currently barely resembles the original mock-ups. (To their credit, those mock-ups showcase a really elegant — if somewhat unoriginal — design that is too unfortunately missing in the RTM builds.)

The current strategy appears to be all too profitable right now for these people to abandon it. We’ll probably just see more development in the GUI design department from web browser vendors than operating systems and desktop environments in the near future.

Whatever happened to my hatred of Firefox

nospam@example.com (shadowmaster) — Thu, 14 Oct 2010 15:20:56 +0000

My collaborators know well that I often refer to Mozilla’s current flagship browser as “Failfox”. Many have read what I’ve got to say about several versions of Mozilla Firefox before. A few also know my stance on the foundation’s trademark policies and their sole existence.

Yet I can’t bring myself to hate this awesome browser that’s still superior to Google Chrome in user interface design as far as I am concerned.

After switching to Iceweasel/Firefox 3.6 from Debian experimental a couple of months ago — after learning of its status at the website of one of the maintainers’ — I have had a pleasing and stable experience with Firefox that I’d not had since 3.0 was released. Now I’m also beta-testing Firefox 4 for Windows on my XP SP3 virtual machine, and awaiting the future stable release.

I thought I’d clarify this for those who might have thought I was yet another Firefox-hater, based on my previous rants. Of course, it’s a bit jarring that it took Mozilla and/or Debian so long to stabilize Firefox on amd64 systems, but I guess you can’t ask for more — it mostly is, after all, a volunteer-driven effort, and amd64 builds had not appeared before in the official FTP server until the Firefox 4 betas, for some reason.