Firefox 3.1 beta cycle pushed back to pack in more features

Firefox 3.1 beta cycle pushed back to pack in more features

Summary:  Mozilla has decided to extend development time of  Firefox 3.1 by four weeks to expand the scope of features in the point release.

TOPICS: Browser

 Mozilla has decided to extend development time of  Firefox 3.1 by four weeks to expand the scope of features in the point release. With that, the team expects the code for beta 1 to freeze September 30 and the code freeze for beta 2 to fall on November 4, said Mike Beltzner, a Firefox development leader.

It’s not clear if the decision to include the new features will move the final release to early 2009.  The Firefox team has stated that the 3.1 release would ship in either late 2008 or early 2009 so this does not constitute a slip. “Beta 1 schedule is still tracking and code freeze [is scheduled for ] September 30,” said Mike Beltzner. “Adding the well scoped features for beta 2 looks like we’re aiming for code freeze in the first week of November. “

During its weekly meetings on Tuesday and Wednesday, Mozilla identified several features now slated to make it into the 3.1 beta 2 including private browsing and several improvements to the tabs functionality.  Firefox 3.1 beta 2, for example, is expected to offer drag and drop for detaching tabs to ease the process of moving tabs from one window to another.

The Mozilla team is also considering integrating other tab features into beta 2. These include tab close animations, showing the tab strip or tab bar by default, a Tab Search function and adding a new tab button to expose more of the tab functionality available in Firefox. Here’s what one Mozilla developer had to say about the a new tab button: 

“The problem is that not everyone knows about the keyboard shortcuts or that tabs even exist. An optional new tab icon in the tab bar would be brilliant because it could introduce new users to a feature they may have never seen before. SeaMonkey has it and Mozilla had it, and the people I know who still use IE use the new tab button. Not many people use keyboard shortcuts and I think putting a new tab button is a strong necessity. I guess the only popular browser not having a new tab button is Firefox.” The decision to add more features into Firefox version 3.1 follows the beta release of Google's open source Chrome browser earlier this month.

Firefox 3.1 Beta 1 will also offer the ability to preview all tabs, among other notable features listed on the Firefox site including performance gains for Places and startup, drag and drop improvements in the library, polish to the password manager and SQLite migration and a tag autocomplete function for the add bookmark dialog box.

In addition to private browsing and tab improvements, the other beta due in early November is expected to feature a refresh of the Windows default toolbar, a video front end, the ability to use asynchronous queries for awesomebar lookups. Still, not all of these features are set in stone for version 3.1.

Late last week, Firefox developer Michael Shaver noted that the team is adding more features into version 3.1 because of increasing competition and the faster-than-expected pace of development of Firefox 3.1.

"There has obviously been a lot of discussion of browsers of late, around Mozilla and around the industry.  Probably the most energetic time we've seen in a decade, if not ever, and it's a tremendous validation of all the  hard work that people have put into Mozilla, and making the browser market more exciting than any monopoly could be. One aspect of the discussion is obviously how Firefox fits into the mix, and what we're seeing is that it fits very well.  The improvements we made in Firefox 3 around performance, security, web platform capabilities, OS integration and even something as "simple" as navigation have resonated very strongly with new and existing users, the press, and developers. "

Shaver added:

"Firefox 3.1 is intended to continue with those themes, to pick up things we had to leave out of FF3.0, and to react to things we've learned in bringing those advances to a skyrocketing percentage of Firefox's coming-up-on-200 [million] users.  And, of course, to continue to learn from what people are doing in other browsers, add-ons, and web applications. " Along the way, we've been pleasantly surprised as a couple of "longer term" projects have shown that they're likely to be ready sooner than we had expected ……   TraceMonkey's early results have led us to some promising plans for DOM and other optimizations in addition to lots of head room on pure JS, and the pace of our private browsing implementation has given us new options for our 3.1 work.  We've also had some great feedback on user interface elements in Firefox 3 that we want to incorporate quickly, and of course we're always watching the competition," Shave r wrote. "Because of the strength of Firefox 3.0, we're not in a rush to get a product to market, and so we've started to look at what we might be able to do with  one more "feature cycle".  We're still hammering out the details, but we know that there is a core list of features that we'll be looking to land between beta 1 and beta 2."


Topic: Browser

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.


Log in or register to join the discussion
  • race to death in sep!!

    Okey, i am care for this many months,but when i try to use firefox 3.1, i am just found it out of my mind,which to hard to say it works good:)

    i can't open web flash video,movies:!!

    <a href="">con't view flash 8 codec movies!!</a>
  • Mozilla starts the photocopiers...

    Mozilla starts the photocopiers...
  • RE: Firefox 3.1 beta cycle pushed back to pack in more features

    FireFoc rocks for so may reasons. Just the sheer number of very useful plugins makes it a winner. <a href="">:)</a>
  • RE: Firefox 3.1 beta cycle pushed back to pack in more features

    I know Firefox is pretty secure already, but as a thought, wouldn't it be better if they didn't extend the beta timeframe *just* to plonk in as many features as possible? Writing code within a short timeframe could mean lack of attention, flaws, bugs and security issues perhaps. Maybe it's just better to release it when it's ready and not be so stringent with timeframes.

    My two penny'worth, more than willing to accept I'm wrong :)
    • RE: Firefox 3.1 beta cycle pushed back to pack in more features

      My read of the article is some of the early changes went so well (and took less time than expected) that they can add more features by just extending the beta cycle by a few weeks. There is also more competition pressure, so meaningful feature additions will help Firefox in the more crowded browser marketplace.

      Firefox 3 is a great improvement over Firefox 2.x in many ways. As long as the "improvements" add security, speed, reliability, a better user experience, and do it without adding bloat, Firefox 3.1 will continue to gain market share.
    • That's what RCs are for

      alphas usually bring in a lot of internal work; it seems alpha stage came off better than expected (JIT, better Acid3, probably some Cairo work too) meaning that the 'easy' part (adding GUI elements over these core features) was actually started in advance.

      'Porn mode' for example didn't require a lot of work, as MobileFirefox and the use of a delayed-commit database tackled both problems.

      So, by delaying beta stage, they can work on internals some more and add more stuff during the beta phase.

      Once that part is done, code is frozen and bugs hunted down during RC phase, until the release is deemed release-worthy.

      And then we'll get Firefox 3.1.1 a few weeks later. As usual.
      Mitch 74
  • New "New tab" button?

    What are you talking about here? My Firefox has had an "Open a new tab" button on the toolbar for a long time (certainly since FF2, maybe FF1.x [I don't remember clearly, too long ago]). What is this new "New tab" about, if not that?
    • Re: New "New tab" button?

      The "New Tab" button is in the "File" menu by default; to put one on a toolbar is an option. I've got one, you must have customized your toolbar so long ago you forgot you did it.

      Anyway, there's not much code to write, just make it default instead of optional. "Private Browsing" is already available from extensions, they just need to decide what version to implement. None of these changes are very involved, really.
  • Even those who don't use Google Chrome

    can be grateful for the impetus that release of this early beta seems to have given - as Paula hints (?[t]he decision to add more features into Firefox version 3.1 follows the beta release of Google?s open source Chrome browser earlier this month?) in the article - to the development of [b]Firefox[/b]'s excellent browser. Competition does indeed seem to be a good thing !...

  • RE: Firefox 3.1 beta cycle pushed back to pack in more features

    This new tab button thing is not a big deal. I use The Gray Modern 2 theme, it has a new tab button.
  • Tab closing animation

    Yeah!! what a gain of productivity will this feature add!

    i even wonder how i could live with my browser without this once in a lifetime invention

    Seriously: integrate tabmix plus in the core browser, this will help much more that all that sand in the eyes
  • I hope it doesn't crash like Firefox 3.0

    Firefox 3.0 crashes all the time on close. I never had a problem with Firefox before this.