digg

Facebook Connect Join Digg About

Reports of Firefox 3.0 bugs overblown, most significant bugs squashed

arstechnica.com — A recent New York Times article erroneously stated that 80 percent of the bugs in Firefox 3 would not be fixed. Mozilla representatives have responded in an effort to illuminate the real situation.

Who dugg this? Made popular Nov 21, 2007

Digg DudeWhat is Digg?

Digg is a place for people to discover and share content from anywhere on the web. Digg surfaces the best stuff as submitted and voted on by the community. Take the Tour to learn more.

46 Comments

show profanity settings
expand all
  • diggerydoo471, on 11/21/2007, -0/+40Wait... a beta has bugs? No way.
  • corevette, on 11/21/2007, -0/+22i dugg it because i liked the article
  • BlackSheep720, on 11/21/2007, -7/+29dugg for the pun "most significant bugs squashed."
  • dillyhoo, on 11/21/2007, -0/+15Dugg for the witty and fitting reference to vacuum tube computers, "bug."
  • duckyinc, on 11/21/2007, -2/+14"A look over the actual list of Firefox 3 blockers reveals that the bug reports don't all actually reflect bugs. Many of them relate to feature requests, performance improvement goals, and corner-case rendering issues that only affect specific web pages."
    How about giving us a percentage of all requests and real bugs?
  • Bamborzled, on 11/21/2007, -0/+117 tabs open, 4 of those are of Digg, Adblock Plus, NoScript, and only 80MB of memory. Sure it could be better, but this is a great start.
  • ajamison, on 11/21/2007, -0/+10Working beautifully here at work on XP, it's noticeably faster. Add in AdBlock and NoScript are working already, and it's a done deal.
  • CamZak, on 11/21/2007, -0/+9The good: It's a lot zippier.
    The bad: I've had it crash on me while trying to go to youtube. System became unresponsive to the point that an xserver restart didn't help (terminal didn't want to open). But I'm on a slow PC anyways...

    But it's good to see that instead of focusing on adding more pointless features that I don't need, they're putting a focus on adding speed.
  • andycr512, on 11/21/2007, -0/+8Works great with multiple Digg tabs, little to no slowdown. I'm using it now. It crashes rarely.
  • Audacitor, on 11/21/2007, -0/+7"Firefox community coordinator Asa Dotzler has characterized such claims as 'horses***.'"
  • schnikies79, on 11/21/2007, -0/+6I don't usually like to mess with beta anything, but I did try this out.

    Aside from none of my extensions working, it seemed nice. I couldn't see a lot of obvious differences.
  • mvent2, on 11/21/2007, -0/+5A beta is not ready for prime time? You don't say...
  • Ancestor, on 11/21/2007, -0/+5There's no easy way to count it, because there is no tag in Bugzilla for this purpose. You'd have to check these bugs one by one.

    Anyway, there is also another reason why this statistic is very misleading. Even if 80% weren't going to be fixed (which is not the case), it would be 80% of bugs remaining AT THIS POINT. Given that 11,000 bugs have been fixed so far, it would be less than 5% of the OVERALL number. A week before the release probably 99% of the remaining issues won't gonna be fixed, so what?
  • bmartin, on 11/21/2007, -1/+5Why aren't you using Gmail yet?
  • ian9outof10, on 11/21/2007, -0/+3I think the Flash Plugin is BADLY broken. I suspect this is Adobe's fault, but it might be the way the two interact.
  • gildude, on 11/21/2007, -0/+3Wait for the RC?
  • SquireToad, on 11/21/2007, -1/+4Tried it as soon as I heard about it. Within minutes my entire system slowed and then locked up with an obvious memory leak.

    Fageddaboudit. Not ready for prime time. (This is a Win2K system, by the way, with a 2.8MHz Pentium IV and 1GB of RAM.) Put the old Firefox back, everything just fine.
  • Peterix, on 11/21/2007, -0/+2Have you tried using Nightly Tester Tool addon? Most of them work just fine when you force them to work.
  • SuckMyDigg, on 11/21/2007, -2/+3Dear New York Times,
    What the hell do you care?
    Signed,
    SuckMyDigg
  • cwcheang, on 11/21/2007, -2/+32.8Mhz? Can't blame Firefox 3. ;-)
  • ErikHK, on 11/21/2007, -0/+1ctrl-alt-backspace?
  • justAnother9, on 11/21/2007, -1/+2hmmm. that's a novel concept.
  • supaklaw, on 11/21/2007, -0/+1Don't throw out 2.0, put it that way. A lot of good improvements though.
  • catt231, on 11/21/2007, -0/+1I'm used to using mouse gestures, forget by accident that they don't work and try to go back a page and it crashes... but it is a beta! that's what's expected... can't live with the bugs don't use it yet!
  • jerbaker, on 11/21/2007, -0/+1Um, the drivers are the ones who are supposed to approve that as a blocker. If they don't like it, they shouldn't approve the blocker nomination. I don't know about you, but it seems pretty lame to me to bestow upon a bug the blocker status and then bitch about it later when you don't even fix the bugs you yourself marked to be fixed.

    Just because a bug isn't significant to you doesn't mean it isn't significant for anybody. This is precisely how the Mozilla staff have become expert at alienating people from their project. Some behave as if they are little fiefdom of programmers with no compunction about refusing to fix significant bugs on grounds of petty personal issues. Ever seen someone who just likes to control things for the sake of controlling things? Just look at Stuart and the removal of MNG support. It was ostensibly removed to assist in making Mozilla, and then Firefox, smaller. When contributors were able to shrink the MNG support down to less than a few kilobytes, Parmenter refused to reinstate it all while refusing to explain any rational basis for excluding it.
  • foofiejnooner, on 11/21/2007, -0/+1Hmmm... Isn't that why its a BETA anyway?? It's supposed to have bugs.
  • saisumimen, on 11/21/2007, -1/+1Thanks for the status report.
  • natalvc, on 11/21/2007, -1/+1Had this exact same problem twice now today (on XP Home). Sticking to 2 as well.
  • trogdoor, on 11/21/2007, -1/+1So you think that "[MacOSX] status bar resize widget not drawn over pinstriped background"

    *should* be a release blocking bug?
  • guy6600crazy, on 11/21/2007, -5/+5Firefox 3 beta is good. But still most of the add ons wont work in it! Anyway i am happy that atleast AdBlock plus and No script works in it.
  • havanese_boy, on 11/21/2007, -1/+1FIX the Memory and I'll give you my first born
  • jerbaker, on 11/21/2007, -3/+3"A look over the actual list of Firefox 3 blockers reveals that the bug reports don't all actually reflect bugs. Many of them relate to feature requests, performance improvement goals, and corner-case rendering issues that only affect specific web pages."

    My favorite way to fix bugs is to define them out of existence. That's apparently the way Mozilla Corp. likes to fix them too. Why don't they produce a list from Bugzilla of bugs with the most votes, and ones that have been there the longest and start on those?
  • inactive, on 11/21/2007, -3/+2I can't right click without a "Crash! Bang! Boom!" message. Then it won't let me send the error message to them. :( This is on the Vista partition, dunno about the Linux one yet.

    http://i18.tinypic.com/7x2zzoi.jpg
  • Fooby, on 11/21/2007, -1/+0I downloaded it and it still ***** hangs every five seconds/page load. Any hints?
  • jimbo92107, on 11/21/2007, -2/+0Loaded FF3 on a vista notebook. My home group is twenty sites, it churned and churned, gobbling ram like a slut. Slap dat bitch and plug its holes, mozilla!
  • guy6600crazy, on 11/21/2007, -2/+0I use Gmail, Hotmail, Yahoo Mail Beta and Thunderbird. Gmail is good but that doesn't mean i should refrain from using other email accounts. And i love firefox, for the same reason i want it to be always perfect.
  • guy6600crazy, on 11/21/2007, -4/+2The thing which made me switch back to FF 2.0.0.9 from 3 Beta 1 - Yahoo Mail Beta persistently reports many Login errors when browsed with 3 Beta 1. Lets hope it will be corrected soon. Till then, m happy with 2.0.0.9
  • nexah3, on 11/21/2007, -5/+2Can't wait to give this a try when I get home.
  • neosublime, on 11/21/2007, -8/+4Who cares...

    Safari FTW
  • TheGreatBelow, on 11/21/2007, -6/+2This beta is pretty bad. Launched it on a fresh install of Vista x86 Ultimate and started browsing around the internet and all of the sudden it started heavily lagging my computer. I check task manager and firefox.exe was using 630MB of RAM and climbing. It hard froze my computer before I could end the task. Sticking to 2.whatever until they release a stable build.
  • htiawe, on 11/21/2007, -5/+1Sorry, it wont happen.
    See, in FF 2.0 it was a feature but in FF 3.0 its a requirement.
  • Veritas77, on 11/21/2007, -8/+3Dear Firefox,
    Screw new features. FIX THE F*CKING MEMORY LEAKS.
    Thanks.
  • inactive, on 11/21/2007, -6/+1Yeah, but will it work with multiple DIGG tabs?
    Just started with opera, no problems. I'll let someone else work the bugs out of FF for now.
    Y'all holler when it's ready.
  • inactive, on 11/21/2007, -7/+2Shades of that stupid "WINDOZE 2000 SHEEPED WIT 6 GAZILLIONS BUGGS OMG LOLOL!!!" meme.
    I guess when you "frame it in the right context" it always makes sense.
  • Jareth86, on 11/21/2007, -8/+1I plan to switch to FF3 as soon as the macfox theme is compatible with it.

  • Add a Comment

    Login or register to comment!
    Or, sign-in super fast with your Facebook account ...

© Digg Inc. 2009 — Content created and posted by Digg users is dedicated to the public domain | Terms of Use Updated | Privacy Policy
DIGG, DIGG IT, DUGG, DIGG THIS, Digg graphics, logos, designs, page headers, button icons, scripts, and other service names are the trademarks of Digg Inc.