Firefox 29 and Australis

In the post yesterday we asked if the screenshot below was that of Firefox or Chrome.

The answer is Firefox. Firefox 29 Beta 1 release with the new Australis theme/UI. This is the first major UI change since Firefox 4 was released on March 22, 2011 (after over a year of developmental releases). Firefox 4 also introduced Tabs on Top, the hidden menu bar and the Firefox button, which with Firefox 29 will be a thing of the past. Kind of a shame too as it at least made Firefox standout from other browsers which are really all starting to look the same now.

Like Thunderbird and Chrome there is now an app/menu button. In Firefox (and Chrome) it is on the far right side of the main toolbar. However, I was rather disappointed with the limited number of options in this menu compared to that of Chrome and for the matter Thunderbird. As you can see below there are a handful of options and they are displayed as icons with small text.

Firefox 29 App Menu

Firefox 29 App Menu

I really don’t understand as to why Mozilla chose to put so little on the new Firefox app menu, especially if you compare below to what options are on the current Firefox 28 Firefox Button menu along with the app menus of Thunderbird 24.4.0 and even Chrome.

Current Firefox App Menu

Firefox 28 Firefox Button (App) Menu

Thunderbird 24.4.0 App Menu

Thunderbird 24.4.0 App Menu

Google Chrome App Menu

Google Chrome App Menu

While you can add options to the new app menu, it is limited to toolbar buttons that are not already on a toolbar. With the lack of options in the new app menu, people are going to want to keep or restore the menu bar. You can re-display the menu bar by right-clicking on the tab bar and selecting Menu Bar. You can also display the menu bar temporarily by pressing the ALT key.

In Chrome as well on my Firefox “Release” profile (Firefox 28) I have my navigation buttons as follows: back-forward; stop/reload; home. So, I was rather irritated when I updated my “Beta” profile to Firefox 29 and discovered the following: the back button is hidden if you can’t go back; the back button (when visible) and the forward buttons are “attached” to the urlbar; the stop/reload button is also “attached” to the urlbar on the right-side; the home button is now on the far left. It wasn’t long before I was accidentally clicking the home button when I thought I was clicking the back button (at least where I was use to the back button being located).

A while back Gareon wrote about the Classic Toolbar Buttons add-on by Aris. I gave this try and while it did let me “detach” the back-forward button from within the address bar, they were still “attached” as in they could not be moved. The same applied for the stop/reload button too. After a little more hunting I found another add-on by ArisClassic Theme Restorer (Customize Australis). With this add-on you can restore squared tabs, appmenu, add-ons bar, small button view and more on Australis UI. There are lots and lots of customization options with this add-on, so you can setup Firefox pretty much anyway you could possibly think of (which is rater ironic considering this was the big claim to fame for Firefox when it first came out).

 photo options-1.png

Main Options Menu on Classic Theme Restorer

I don’t mind the new tab style, so I went ahead and opted not to restore the square tabs. I did restore the old Firefox App button and made it icon (which is different from that of Firefox 28) only on the titlebar. Movable back-forward button allows you to “detach” the button(s) from the urlbar. The Hide urlbars stop & reload buttons option is somewhat confusing, but it has to do with the way stop & reload buttons are “connected” with the new theme. Checking this option will remove the button(s) from the urlbar. Then, you can right-click on a toolbar button and choose Customize… Grab the stop & reload button(s) and drag to where you want the button(s) on your toolbar. The end result of my customization is below.

 photo classictheme.png

 

So much like Windows 8 (with Classic Shell), Firefox 29 and Australis are bearable once you install an add-on and do a little tweaking. The two add-ons can be used together if you choose (I don’t mind the newer buttons so I opted not to use the buttons one). The Classic Toolbar Buttons can be used with Firefox 24 or newer and installs without a restart. However, Classic Theme Restorer can currently only be used with Firefox 29 Beta or any of the other current developmental builds (Firefox 30 Aurora and Firefox 31 Nightly) and will require a restart when installed. Once Firefox 29 has been released, you will need to update to Firefox 29, then you will be able to install the Classic Theme Restorer add-on, restart then customize your Firefox to your liking.

One more thing…a teaser of sorts…Firefox 29 is supposed to include a “new and improved” version of Firefox Sync. I have never had much luck with this feature before, which is why I have been using Google Chrome on most of my devices. I just need to install Firefox 29 Beta on my laptop and tablet, then I can try out this feature.

 


Comments

Firefox 29 and Australis — 17 Comments

  1. Pingback: The New Firefox Sync (Firefox 29) | Firefox Extension Guru's Blog

  2. The frustration I have had with Mozilla is their complete refusal to establish and maintain a distinct and unique appearance versus IE, Chrome, Opera & Safari. Now with Australis, it is the height of ridiculousness that a so-called independent project such as Mozilla Firefox would willingly choose to make itself look like its major competitor, Google Chrome.

    Add on top of that that Mozilla would think that those of us who use Firefox on non-touch screens would actually like the waste of screen real estate that is the new hamburger button. The final strike against Australis is the dropping of the addon bar. For a browser whose key selling point is customization, why drop the addon bar completely from it while copying Chrome by forcing buttons normally placed on the addon to have to hide behind another menu button on the nav bar?

    I have been able to “restore” Nightly, Aurora and now Beta to the rough appearance I had with the previous default theme by using CTR (with CTB) from Aris–thanks a million for your hard work, Aris–but I have to ask Mozilla why they did not offer Australis as separate addon theme first. Could it be that by not offering Australis as a choice to users, Mozilla avoided being embarrassed when too few, if any, users opted for Australis?

    • Chrome’s look and feel was based off the initial research done years ago by Mozilla – they just implemented it first before Mozilla finally did. So you’ve got the situation entirely backwards.

      How does the hamburger menu take up significantly more space than the firefox button or menubar did?

      It’s not offered as just a theme, because they rewrote huge parts of the UI code along with the look/feel changes, making it cleaner, faster code which also gives addon/theme designers *more* capabilities in modifying it, so you’ll see more done with it in the future than currently.

      • Perception is reality. Whoever conceived curved tabs, it does not matter. Google beat Mozilla to market with curved tabs and only years later do we see them in Firefox. It does not matter that the idea was originally Mozilla’s. All anyone will see is that it looks like Firefox copied Chrome, thus, invalidating your criticism.

        Your question/comment about the hamburger menu is ridiculous. Of course, the hamburger menu covers much more screen real estate that what it is supposedly an improvement upon. That makes is a complete and utter waste to keyboard and mouse systems which will always be more efficient than touch screens.

        The entire concept of the hamburger menu is solely touch-centric. As Microsoft is finding out the hard way with Windows 8 and its updates, many are not accepting touch-centric because of its inefficiencies. Indeed, rumor has it that when Windows 9 comes out, there will be different versions geared towards the specific device be it a touch screen or keyboard and mouse device.

        Taking away things like the addon/status bar is not an improvement. It has angered the many thousands of users who have installed addons like Classic Theme Restore and others that return the addon bar to Firefox. Why was it so difficult to leave the addon/status bar code in? What value was gained by removing it?

        Also, if “improvement” was the goal, why weren’t addon and theme authors consulted on this? As I understand it, nothing was done to create a standard for addon authors to follow when creating buttons and toolbars for their addons that would not conflict with the UI in unpredictable ways.

        In fact, truth be known, instead of consulting with serious users like those of us who frequent places like the mozillazine forums, many developers look down their noses at us. They see us more as pains in their behinds than as valuable resources who can, in fact, make Firefox a better browser.

        In fact, I have had my own experience where I questioned the wisdom of removing a few lines of code regarding the choice of where the tab close button goes. This was a hidden preference accessible only in about:config. A lone developer decided that even though it was a hidden preference its apparent lack of discoverability was reason enough to remove the code. Of course, when it landed in Nightly, it broke a fairly popular addon, Tab Mix Plus, rendering the browser unusable until TMP was either disabled or patched. When it was pointed out that the removal of the hidden preference affected addons like TMP and was the effect on addons considered before OKing this change, the response basically was that the developers could not care less if their changes affected addons; that it was up to addon authors to update their addons when changes in the browser broke their addons. So, for no real “improvement” in the browser, a change was made that had the negative effect of breaking addons and the developers could not care less that the change caused this.

        To me and others like me, this is all about the lack of proper leadership. Proper leadership would lay out a series of questions or bullet points that any and all changes would have to be evaluated against. Right up at the top is a comparison between improvement/positive effects vs. negative effects (including how the change might impact addons forcing authors to repair their addons). I look at Australis and conclude that nothing like this was ever done.

  3. Mozilla is trying to build the windows 8 of the browser world, if I wanted to use Chrome, I would be using it already. If I have to use all kinds of ad-on software I will just go t chrome. Just like I bought a new computer with windows 7 instead of windows 8.

  4. I ended what seems like a decade of using Firefox as my main browser about 18 months ago in favor of Pale Moon x64. The advantages were two-fold: a frozen interface and the fact that it worked with add-ins that newer versions of Firefox broke (mostly permanently). Still, I kept my Firefox current, mostly to deal with issues arising at the office. I had beaten it into their heads that IE was not to be used without court order and I thought most of what Firefox was, continued to be. I started the process of switching all users to Pale Moon on the weekend (cheating by CALLING it Firefox and using a vaguely Firefox-like icon) just to avoid the mass hysteria going against my oft-stated wishes might cause. I will have completed the process before Australis comes out. For me, Firefox ceases to exist come the release of the product after Firefox 28. Sad to see it go, to see it become a second-rate Chrome. Chrome does Chrome better than Mozilla does. Tis true and nothing the silence from the Mozilla doyens does changes that. I’m angry about the extra work, but it’s the sheer pointlessness OTHER than to legitimize some continuing design and programming jobs that bothers me the most. I really wish somebody from on high would publish a rationale for this … I’m out of words.

  5. It depresses me greatly realizing that Firefox has gone off the track of what I like, as Opera did years ago, and that there’s no option I like. Having to use tons of extensions and about:config modifications to make it how you want and deal with it’s constant updating over non-security releated matters which may break extensions is a pain.

    This update might be the one that drives me to Chrome or even IE. If you’re going to hate your browser anyway, might as well go with the easiest or most popular.

  6. Out of all the unnecessary tweaks to the UI of the new Firefox 29 I was forced to enable this afternoon, I wish there had been a “Uninstall New Clusterfuck Version” button. I still can’t find my status bar.

  7. The most saddening/madding thing is the claim that they’ve made Firefox ‘easier’ to tailor, yet actually stood on their heads to do the opposite. (Worse is the official forum’s propensity to lock any thread that dares express dismay.)

    My particular ‘beef’ is the joining of the ‘bookmark this page’ and ‘show bookmarks’ buttons (with the rationale that people didn’t realize the meaning of the ‘star’ image). Just because two buttons relate to the same function (bookmark list) does NOT mean they have to be co-joined. Moving the cursor to the ‘display bookmarks’ now runs the risk of bookmarking the current page instead!

    ‘Fixing’ the reload button into the url bar is another example of this ‘restriction in the guise of flexibility’ irrationality..

  8. what the Fuck, FF is like a 2yr. who shits & pees on the floor, they keep changing, all the time, move this move that, oh, oh! like make it look like chrome, or feel. if you keep changing brand design why, why, you change the basic look, I have know idea, who the fuck you are anymore.
    . FF 29 junk and more crap, you just keep fucking with my head on new updates, now go back to the bathroom & clean yourself up

  9. I am not changing to chrome because I do not trust google! I have using Mozilla since
    it came out as Netscape, when Gates was saying their was no need for a browser, the
    next version of windows included I.E.. I am staying with Mozilla, I am sure that the negative
    feedback they are getting will light a fire under the develop team.

    • Tom, would that you are right on this issue? But criticism seems to fall on deaf ears. In part because Firefox is now a runaway train with three versions in the pipeline and a furnace to feed every six weeks, right or wrong. PLUS, there have been comments that the consolidation of user experiences into a single button has been a day-one design goal of the Mozilla team. The deafening silence, the continued fiddle-faddle make-work interface makeovers and increasingly failure of popular add-ins with these new versions makes continued devotion to the ‘ideal’ of Netscape/Mozilla Firefox a rather ostrich-like response. I’ve switched to Pale Moon to fight off the impending end of the usefulness of Mozilla code. But I’m also spending extra time with Chrome seeing if i can make it as bullet-proof as Firefox used to be. The fact that I’m upset simply does not register with the company. They don’t care. They think I will ‘come around’ since I’m supposed to not have any alternatives. Can you really trust a company that comes to that supposition? I don’t. I applaud your loyalty. But where is Mozilla’s loyalty to you not to destroy the product you’ve used instead of Internet Explorer, Opera or any of a gazillion other lesser know/used alternatives? I’m on my fifth web browser, fourth firewall, seventh anti-virus program and fourth different OS. Technically five, if you count my Android tablet. Times change and clinging to our old IBM’s or DEC’s is more admirable than wise. Please re-consider. At least check out Pale Moon.

  10. When developers insist that updating is critical to the security of a platform, a user base, the internet community as a whole… that’s all fin and fair and understandable.
    BUT – when they lump in various non-security-related features/functions/changes… they become liars (IMHO). THEN – when they start “silent” updating folks against their will, or “firm push” updates… or any other alterations they know are unwanted by the user/OWNER of the resident device… then they become (IMHO) the very essence of malware. Since firefox has always been (purportedly/intentionally) secure – ANY security vulnerability is by its nature a “defect”. We’re not “laggards” just because we don’t trust your efforts to repair your product’s defects after you’ve exposed to them in the first place.

    This is where Microsoft keeps getting it wrong (IMHO). Anything that is installed on my box – I reserve the sole-discretion right to “not update” and/or to “not delete” if you decide to pull the version.

  11. I don’t understand – why All new browsers try to be the same as f..cking Chrome. Race with version numbers, no separate stop/reload/go buttons. Try to work without it on tablet without keyboard!

Leave a Reply