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. Not to complain... by dmayle · · Score: 5, Informative

    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 (In 0.8 I rarely had the problem, under 0.9.3 under three different operating systems, (and three different microarchitectures) I get it more times than not on Slashdot articles and comments.)

    Granted, I won't give up the best browser I've ever used, but it's getting to be really annoying.

    And come on, we all know that the Mozilla devs spend more time reading Slashdot than anything else, so why hasn't it been fixed yet?

    1. Re:Not to complain... by colinramsay · · Score: 4, Informative

      http://bugzilla.mozilla.org/show_bug.cgi?id=217527

      That's the bug. It's fixed on the main trunk but not on the Firefox 1.0 branch... yet.

      --
      Free iPods - now in the UK!
    2. Re:Not to complain... by 0x0d0a · · Score: 4, Informative

      It is definitely a Gecko bug (the rendering component of Mozilla and Firefox) relating to incremental reflow, not a problem with Slashcode. It's not something to be glossed over. On the other hand, as others have pointed out, it's fixed in Gecko -- just the fix hasn't been rolled into Firefox.

      In the meantime, you could try disabling incremental rendering (at the cost of potentially greater delay until a web page is in a readable state) and see if that works around the problem: go to about:config and add a boolean value for content.notify.ontimer and set it to false.

      There's some random Firefox-related discussion on a forum here. While these people don't really know what they're talking about, they do nicely list the incremental reflow prefs that you can play with. You might be able to come up with a reasonable workaround until the fix gets rolled in.

      Remember to set the prefs back when you update Firefox to a fixed version -- you don't want to be either burning CPU time like mad or waiting longer than you need to to be reading pages.

      --
      May we never see th
    3. 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.

  3. Meta RC by reignbow · · Score: 4, Funny

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

    --
    Divide et impera!
    1. 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
  4. unprecedented grassroots campaign? by foniksonik · · Score: 4, Funny

    "unprecedented grassroots campaign"

    Read this as "we'll be posting announcements on Slashdot every day for the next month"...

    --
    A fool throws a stone into a well and a thousand sages can not remove it.
  5. Re:Change log? by Anonymous Coward · · Score: 4, Informative

    http://www.mozilla.org/products/firefox/releases/0 .10.html http://www.squarefree.com/burningedge/bigger-pictu re.html#newin1.0pr1

  6. Re:What I hate about Mozilla Firefox for Windows.. by SecretMethod70 · · Score: 4, Insightful

    If Firefox wants to be a popular browser, it needs to fix this bug for that very reason. Porn drives the internet, and if a person's browser crashes or crawls to a halt when they're looking at porn, they're not going to stick with said browser. They'll go back to IE, where they can look at porn (and also get viruses) more easily. This bug is probably one of the most important bugs in Firefox that needs to be fixed, and it's been there for a LONG time now.