Firefox 3.1 Beta 3 Coming on March 10


Recommended Posts

Yesterday Mozilla updated its release schedule to include Firefox 3.1 Beta 3, set to go live on March 10th at 2pm PST. Whether or not it actually lands in the hands of public end-users is another question.

Believe it or not, Firefox 3.1 hasn't seen a major upgrade since June 2008, however hopeful users seeking new features and improvements of the Internet browser can expect to see Beta 3 to go live on March 10. This is, of course, will only happen if the current version actually went into code freeze last night, and Mozilla kicks off the QA testing later today as originally scheduled.

So what's taking the new beta so long? According to this blog post by Mozilla's vice president of engineering Mike Shaver, the "upvar" patch and a handful of other JavaScript patches have held up its release. "That patch is getting close, but the continuing and great work on fixing other final-release blockers means that we're accumulating a lot of changes on the 1.9.1 stream that would benefit from wider feedback from our beta testers," he wrote in the post last week. "To that end, we're going to wrap up beta 3 in the next week regardless of upvar status."

Last week, Shaver also mentioned that the team decided to release a fourth beta, scheduled to hit the public six weeks after Beta 3's release. This fourth beta will serve as testing grounds for Mozilla's new TraceMonkey JavaScript engine, video, Places and "other eagerly-awaited improvements as well as feedback from Beta 3." This announcement also confirmed Shaver's statement from weeks ago, saying that bugs in the TraceMonkey engine were slowing things down, and that the developers were considering a fourth beta.

But as of Monday night, Mozilla had not completely resolved the TraceMonkey issue, thus consumers will see Beta 4 addressing those issues when released in April. Progress of Firefox 3.1 has been fragmented since its original 2008 launch date, held back by various bugs and the development of TraceMonkey. Just this year alone, Beta 3 experienced two major setbacks, first in mid-January and then again a week later. However, several Firefox developers felt that Beta 3's development process was taking too long, especially in light of TraceMonkey.

"Without Tracemonkey, we probably could have shipped 3.1 (final) by now (or, if not now, within the next month), since other areas would have been under more pressure to finish sooner," said David Baron back on February, "and since some of the things we've been adding to the blocker list lately (in Layout, anyway) feel a lot more like 3.1.0.2 blockers than 3.1 blockers."

Hopefully Mozilla will stay true to the schedule and release Beta 3 on March 10. However, more delays will only keep Firefox from gaining ground once Microsoft releases Internet Explorer later this month; Apple's Safari 4 went into public beta last week.

Source: tom's hardware

Link to comment
https://www.neowin.net/forum/topic/742800-firefox-31-beta-3-coming-on-march-10/
Share on other sites

IE8 is actually already finalized on Win7 Build 7048, so the RTM could likely be just days away. But I do think that 3.1 will go final before Safari 4.

Not at this rate, i think safari 4 will have another beta before going final and SF 4 willl be released before Firefox 3.5 goes final. the third beta has been pushed back to March 12. and Firefox will now go from 3.1 to 3.5. beta 3 will still use the 3.1 number. and they will be a beta 4. Here's the Status on all this.

If they continue like this, then Opera 10 final will come out before FF 3.1 final :p

I wouldn't be surprised by it, see my above post.

A first test build of Firefox 3.1 beta 3 is now available:

http://ftp.mozilla.org/pub/mozilla.org/fir...didates/build1/

Also, according to the notes from the last Firefox status meeting will be released as version 3.5 rather than 3.1 'to indicate increased scope'.

A first test build of Firefox 3.1 beta 3 is now available:

http://ftp.mozilla.org/pub/mozilla.org/fir...didates/build1/

Also, according to the notes from the last Firefox status meeting will be released as version 3.5 rather than 3.1 'to indicate increased scope'.

Thanks, and it's about time.

Also, according to the notes from the last Firefox status meeting will be released as version 3.5 rather than 3.1 'to indicate increased scope'.
No, the notes clearly indicate that they are just considering it at this point. No confirmation anywhere.

I tried out the new tab add-on, and it seems to have some promise. Problem is, it doesn't appear to play nice with other extensions, such as the always needed TabMixPlus, and one of my favorites, Fast Dial. It would be pretty cool if there's a way to get them all working together. Anyone know of a way? Perhaps an updated TabMixPlus that plays well with this new tab add-on.

Let me know! In the meantime, I'm going to mess around with it in hopes of figuring something out.

The build 2 that u mentioned, does it work with the most commonly used extensions? Such as TabMixPlus and Fast Dial. There's no point in downloading that if Beta 3 is coming out on March 12th, right? Does it have the new tab behavior built in?

I don't know, I tend use IE more than I fo Fx; and anyways a Extensions compatibility checker will popup if the extension does not work...and I don't know how to check if the new tab stuff is in it or not...you may have to look at the stuff in about:config.

The build 2 that u mentioned, does it work with the most commonly used extensions? Such as TabMixPlus and Fast Dial. There's no point in downloading that if Beta 3 is coming out on March 12th, right? Does it have the new tab behavior built in?

Fast Dial is compatible, and they'res a Tab Mix Plus development build that's also compatible.

The Nightly Tester Tools extension can make most extensions work with beta 3.

Thanks for posting that, Binary! It seems TabMixPlus auto-updated to the newest version. Now I'm just trying to decide if it's worth it to update to 3.1 beta 3 pre-release, or just wait til beta 3 is officially released? That's supposedly gonna be on March 12th. Might just wait if there's no big reason for me to update.

The releases of Beta 3 are just nightly releases. It has not been officially released as Firefox 3.X Beta 3 yet.

https://developer.mozilla.org/devnews/index...ome-firefox-35/

The much awaited launch of Fx3.1 Beta 3 is now in the hands of QA for testing. We are working hard to target ship by 3/12 now, pending any blockers found. BetaTesters, we'd love your extra help on these beta 3 candidates! Please download a beta 3 candidate and give it a testrun. All bugs found should be investigated for dupes first, and then filed under bugzilla. Note that these are not official, until QA has signed off on them, and the announcement is made on Mozilla Developer News.

http://quality.mozilla.org/events/2009/jan...31-beta-3-ships

What was the point in posting that when I just said above that it's coming out March 12th? You made it seem like you were correcting someone. We already knew that.

I did not mean to. I would not however bet any money on it being out on March 12th. It has been delayed so many times there is no tellin when it will be out. They even had to rename their numbering release scheme due to the delays. On the site that I quoted, it said it would be out late Feb, then it was delayed until March 2nd, and then it was posted that it would be out March 17th. Now it is March 12th. Maybe someone should start a poll and give out a prize to whoever guesses the correct release date of Firefox 3.5 Beta 3. :)

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • Microsoft launches Godot Sample to streamline Xbox PC game development on the engine by Pulasthi Ariyasinghe Microsoft today announced a new endeavor that aims to make it simpler for Godot developers to get their products into the Xbox PC ecosystem. Dubbed the "XBOX Godot Sample," this is a new public reference for developers using the open-source engine. This is set to serve as an example of how Microsoft GDK, Xbox Services, and PlayFab can be integrated into their projects. The sample is available now on GitHub as a working example. This covers key features in gaming projects that developers may need to release their projects on Xbox PC, with everything from matchmaking and game sign-in to gamepad compatibility with Godot being covered. This release is being called the first step in giving Godot developers the tools to bring their games over to Xbox PC, with more changes to come based on feedback and issue reports. However, the company was clear that this is not related to bringing Godot projects to Xbox consoles. The engine's open development model stops it from accessing console SDKs due to the requirement of NDAs and legal contracts. Here's how it explained this Godot sample project's focus: This is a source-only sample, not a product. It's MIT-licensed at the wrapper layer; the GDK and PlayFab dependencies still require their own installs and license acceptance, consistent with our other XBOX samples. There is no set update cadence for support or maintenance. We’ll watch the repo, monitor issues, and iterate where it makes sense, but this isn't a commercial release. That said, we’re excited to hear your feedback and see any community PRs, as we evolve this together. This is the first step in bringing Godot for XBOX on PC. We plan to evolve it over time based on what the community tells us is most valuable. This sample is built specifically for XBOX on PC. It doesn’t include support for XBOX Series X|S or XBOX One. If you’re already building for XBOX Series X|S or XBOX One, please talk with your XBOX representative. If not, you can get started by signing up here. Game developers can find the XBOX Godot Sample by heading to GitHub over here. Documentation on how to get started with Godot for building an Xbox PC project can be seen here.
    • I don't understand the vision. Do people really want to buy a new computer from Dell with 6 browsers installed? We all keep asking for Microsoft to stop having so much junk on their OS, and adding a bunch of browsers seems to go against that. Ideally, we would just be asked what browser we want during OOBE but Google is just going to pay Dell a bunch of money to include Chrome. Additionally, would you want your phones to start including all the browsers too when you get them? The only thing I ever wanted was to be able to uninstall IE or edge and I believe you are now able to. I do agree that microsoft needs to chill with their "are you sure you don't want to try edge before you install chrome" ads when going to download chrome.
    • It is notable that around 70% of web browser users choose Google Chrome. However, it is puzzling why anyone on Windows would opt for Chrome when Microsoft Edge is often superior in many aspects and comes pre-installed. Edge collects less data, uses less RAM, and is more optimized for Windows as a native Microsoft product. While some may point to bloat in Edge, much of it can be removed with simple tools, requiring no more effort than installing Chrome. Meanwhile, Chrome reportedly downloads large amounts of AI data (4 GB) without explicit consent. I'm sure you Chrome users love that, or? Here is one example of a tool that doesn't even need to be installed to be able to use: https://github.com/TheBobPony/MSEdgeTweaker Although Microsoft’s aggressive promotion of Edge may be questionable, the browser’s current advantages make it a preferable choice over Chrome today, even if Chrome may have been better in the past.
    • JetBrains rolls out IntelliJ IDEA update with Markdown preview fixes and more by David Uzondu Image via JetBrains IntelliJ 2026.1.3 from JetBrains has landed, bringing several highly requested bug fixes that target common UI glitches and terminal rendering issues. If you run tmux inside the integrated terminal, the IDE no longer renders the cursor above the active line. The Markdown preview bug, which was fixed in this release, had annoyed developers for quite some time, as the preview pane failed to render images saved outside the project directory. Instead of displaying the actual image, the IDE simply showed a broken image icon, a problem that stuck around for two years before this update. Over on Windows, developers running WSL can now use wsl.exe to spin up their environments without losing terminal functionality. In previous builds, launching a terminal shell with something like wsl.exe -d ubuntu inside a Windows-based project broke both shell integration and active process detection. Other bug fixes in this release include: An issue where Gradle sync incorrectly reported success as a failure on WSL when using Gradle 9.5.0. A syntax highlighting bug that flagged valid Java for-loop initialization blocks with multiple statements as incorrect. A warning bug that triggered a false non-null local variable alert when using JSpecify annotations. A database generation bug that hid the option to use a DELETE statement instead of a TRUNCATE checkbox. A Kotlin highlighting failure where an assertion error in the Gradle redundant library inspection broke error highlighting. A UI bug where the ComboBox popup lacked a maximum height restriction. A Snowflake syntax error where DataGrip failed to support the "create temp" command. A Svelte syntax parsing failure that incorrectly flagged quotes inside inline expressions. A VCS repository manager deadlock that triggered thread pool exhaustion. A memory leak where the LazyTree component kept all previous versions of a tree in memory. IntelliJ 2026.1.3 is the third bug fix release for the IntelliJ 2026.1 series. The first one landed back in April with a fix for the WSL Python interpreter freeze, another fix for guest participants using Emmet abbreviations, and corrected WildFly server deployment errors.
  • Recent Achievements

    • Collaborator
      Asgardi earned a badge
      Collaborator
    • Conversation Starter
      mobandz earned a badge
      Conversation Starter
    • Apprentice
      fernan99 went up a rank
      Apprentice
    • One Month Later
      nothanks earned a badge
      One Month Later
    • One Month Later
      B2Proxy earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      469
    2. 2
      PsYcHoKiLLa
      243
    3. 3
      Skyfrog
      79
    4. 4
      FloatingFatMan
      73
    5. 5
      Michael Scrip
      60
  • Tell a friend

    Love Neowin? Tell a friend!