Slashdot Mirror

← Back to Stories (view on slashdot.org)

Firefox 1.0 Preview Release Candidates Available

Posted by timothy on from the cutting-edge-is-the-bleeding-edge dept.

blakeross writes "The preview release of Firefox 1.0 is just around the corner, and we've now got candidate builds available. Please help us bang on these builds to ensure that the preview release is sound and ready to go, as this will be our largest and most public release to date. We're also working hard on an exciting and unprecedented grassroots campaign that will launch with the preview release, so stay tuned."

10 of 88 comments (clear)

  1. Good thing, too. by adolf · · Score: 3, Interesting

    Would you believe that I just reloaded Slashdot in Firefox, right as this article is posted, only to have the thing turn glacial and unusable?

    You'd think we'd be farther along than this after a decade.

    Let's hope that the new Firefox RC series Doesn't Suck. (That earlier versions tended to suck less in general than other browsers does not a non-sucky browser make.)

    --
    Kid-proof tablet..
  2. Re:Meta RC by arcade · · Score: 5, Interesting

    So this is the candidate for the preview release for the final release? What is this called? Release Candidate Candidate?

    Personally I think the entire concept of "Release Candidate" has been abused severly in many Open Source projects. A Release Candidate should be released, and if no showstoppers is found it in - it should become the FINAL release.

    I shuddered when KDE had both "RC1" and "RC2" in their release schedule long before they had actually reached that stage. An RC2 should never - in my opinion - be planned on beforehand.

    Anyways. "Final Beta" would probably be a nice name for it. ;)

    --
    "Rune Kristian Viken" - http://www.nwo.no - arca
  3. Re:Not to complain... by cymen · · Score: 2, Interesting

    I managed to trigger it on the main page after 3 reloads.

    Anyone find updates for disabled extensions? Going to hunt down Adblock, SessionSaver, and BugMeNot updates.

  4. Re:Not to complain... by Homology · · Score: 5, Interesting
    Not just to complain..., but has the Slashdot reflow bug been fixed in 1.0? It's been known for ages, but it's recently gotten much worse in 0.9.x

    Security-wise, the 0.9 series are worse as well. Enough so that the port maintainers at OpenBSD will not yet upgrade from 0.8 to 0.9.x until later. OpenBSD will mark the port as broken rather than upgrade.

  5. Re:Not to complain... by cymen · · Score: 2, Interesting

    "You can just use the Tools->Extensions->Update feature."

    I wish. It never works here. For example, Adblock with the update detected an updated version but couldn't install it. All the other extensions weren't recognized as being updated but in fact did have updates.

    Has it these feature *ever* worked for you?

    BugMetNot 0.60 here: extensions.roachfiend.com (mozdev still has 0.50 version that is incompatible)

    SessionSaver & Adblock from mozdev worked.

  6. Re:Not to complain... by 0x0d0a · · Score: 2, Interesting

    Has it these feature *ever* worked for you?

    I think I picked up one update at one point.

    The only problems I've had with updating plugins, really, came when I tried to update a very old version of AdBlock to a newer version and the update really screwed up rendering (a known bug), requiring a lot of hair-pulling and eventually a prefs.js deletion.

    I'm not running into problems ATM, but then I plan to wait to update Firefox until Fedora packages and ships the next version, nicely tested and all.

    --
    May we never see th
  7. how can in be more public? by portscan · · Score: 2, Interesting
    this will be our largest and most public release to date


    Firefox is already at the top of the Mozilla.org website, taking up about 6 times as much space as the full Mozilla suite. There has been no real marketing for Netscape, Mozilla, or Firefox recently, so I am wondering how this release will be more public. Any ideas?
  8. Re:Not to complain... by _xeno_ · · Score: 2, Interesting
    I wrote my own extension, so yes, the update feature has worked for me in Firefox 0.9.3.

    However, it's never displayed as an "Update Available" in the status bar like it's supposed to. If you double click on the "Update" area to make Firefox search for new updates now, it doesn't work either. In fact, the only way it does work is to go to Tools -> Extensions, specifically select my extension, and then choose "Update."

    After that, it worked fine.

    So... yes, it works. Sorta.

    --
    You are in a maze of twisty little relative jumps, all alike.
  9. Re:No source bundles? by Anonymous Coward · · Score: 0, Interesting

    If you're going to the trouble of building it yourself, a CVS checkout is but a minor inconvienience.

  10. Better and Better by jefu · · Score: 1, Interesting
    The new firefox looks great and seems to run great.

    Just two quibbles from me.

    Firstly the tab extensions does not seem to be a supported extension. Now I've read often enough about how it is horrible and ugly and all, but I use it for everyday browsing. I'd really like the default to be "open link in new tab" for just about everything with the middle mouse button set to "open link in this tab". The tab groups are also nice, but could be managed outside the standard tab extensions.

    Secondly, SVG does not seem to be supported yet and I'd quite like it to be. Once a couple of major browsers support SVG, I think it will take off and become a very powerful web tool - but it is going to take that support in some browser.