Slashdot Mirror


Firefox 7.0 Beta Released

An anonymous reader sends word that the first Firefox 7.0 beta has been released. One of the big areas of focus for this version will be performance enhancements. One optimization "Reduces memory use and improves performance areas including responsiveness, startup and page load time, even in complex websites and Web apps." Another addresses one of Firefox users' long-standing gripes: "The JavaScript garbage collector works more frequently to free up memory and improve performance when you have many tabs open or keep Firefox running for a long time."

237 comments

  1. FIrefox 8 Alpha... by recoiledsnake · · Score: 4, Insightful

    Next in few mins...Firefox 8 Alpha released and Firefox 9 Preview released... Do we need to clog up the front page with these articles? Gone are the days of version numbers making any sense in FF. We don't report Chrome versions do we?

    --
    This space for rent.
    1. Re:FIrefox 8 Alpha... by jhoegl · · Score: 1

      The version is a lie.

    2. Re:FIrefox 8 Alpha... by swordgeek · · Score: 2, Insightful

      Actually, I think you meant to say:

      "Gone are the days of...any sense in FF."

      --

      "People who do stupid things with hazardous materials often die." -- Jim Davidson on alt.folklore.urban
    3. Re:FIrefox 8 Alpha... by WitnessForTheOffense · · Score: 1

      Hey, it's better than more troll-bait Google FUD from Florian Müller!

    4. Re:FIrefox 8 Alpha... by Anonymous Coward · · Score: 0

      Not for this recoiledsnake character. His account is pure agenda. Read some of his post history and see if you can figure out what said agenda is.

    5. Re:FIrefox 8 Alpha... by TheDarkNose · · Score: 1, Informative

      Yeah, it's kind of ridiculous... I'm still on FF 3.6

      --
      "Obviously, you need to be an Einstein to navigate the Austrian Patent Office website." - platinumrat
    6. Re:FIrefox 8 Alpha... by Mr.+Vage · · Score: 1

      Don't worry, I have a feeling they'll stop when they hit version 10. They are just trying to get there as fast as possible so that they can change the name of the program Firefox X because X makes everything 20% cooler.

    7. Re:FIrefox 8 Alpha... by mabhatter654 · · Score: 1

      Why on such an old version? There's no reason because Firefox is FREE and it's not like they're making soul-sucking changes to the license lately.

      Firefox is moving to Chrome's release model. There are no more "versions" just the latest, best product they can make right NOW.

    8. Re:FIrefox 8 Alpha... by Anonymous Coward · · Score: 1

      Yeah, we need more space for Bitcoin stories

    9. Re:FIrefox 8 Alpha... by JMJimmy · · Score: 2

      Ditto. Not upgrading any time soon. The UI needs an overhaul in 4+ and something needs to be done about plugins breaking. Plugins are the only reason I use Firefox over other browsers. While other browsers have some, not all that I use.

    10. Re:FIrefox 8 Alpha... by Midnight+Thunder · · Score: 0

      Come December we will be celebrating Firefox 22. and sometime next year it will be Firefox 42 and we will be left looking for a question.

      --
      Jumpstart the tartan drive.
    11. Re:FIrefox 8 Alpha... by tepples · · Score: 2

      Why on such an old version?

      Ubuntu 8.04 LTS won't upgrade Firefox past 3.6.x, and I like to have the same OS on the development and deployment machines. It took a while for our hosting provider to start offering Ubuntu 10.04 LTS on its dedicated servers.

    12. Re:FIrefox 8 Alpha... by sweatyboatman · · Score: 1

      No. Come December it will just be Firefox. No number. You want to know what "version" you're running, go to the About dialog.

      --
      It breaks my pluginses, my precious!
    13. Re:FIrefox 8 Alpha... by smooth+wombat · · Score: 1, Insightful

      As I said in a previous Fx story, not all of us WANT the latest and greatest. Not all of us WANT to be forced to upgrade because we can't turn auto update off.

      It should not be up to the developers to dictate how I use software on MY system. Maybe YOU want to be on the bleeding edge and have the bells and whistles, I don't.

      For a large group of people who rail against authority and being forced to do something by the government, it's amazing how many bend over and take it from the OSS/Free software community when they force shit down people's throats willy nilly.

      Again, rule #1 of IT: Never let a programmer program your application*.

      *Rule #2 is never let a web designer design your web site so it would be redundant to use the word design twice.

      --
      We will bankrupt ourselves in the vain search for absolute security. -- Dwight D. Eisenhower
    14. Re:FIrefox 8 Alpha... by frenchbedroom · · Score: 3, Informative
    15. Re:FIrefox 8 Alpha... by jalefkowit · · Score: 2

      If you want to get more recent versions into your LTS system, Mozilla operates a PPA that you can add to your software sources that will bring the most recent stable version of Firefox and Thunderbird into your next system update.

    16. Re:FIrefox 8 Alpha... by Bengie · · Score: 1

      The version numbers make perfect sense and do exactly what they're suppose to do... The larger the number, the "newer" it is.

      I could care less what kind of numbering system the use, so long as it's incremental.

    17. Re:FIrefox 8 Alpha... by Bengie · · Score: 2

      FF5 didn't upgrade to FF6 automatically on any of my machines. It did tell me that there was an update, but it didn't force anything. Chrome's auto-upgrade can be turned off, they just don't make it easy to the end user because 99% of the time, it shouldn't be. Anyone in IT should easily be able to disable this.

    18. Re:FIrefox 8 Alpha... by arose · · Score: 5, Insightful

      It should not be up to the developers to dictate how I use software on MY system.

      Then get the source and do whatever the hell you want. YOU don't get to dictate what THEY do.

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    19. Re:FIrefox 8 Alpha... by ProzacPatient · · Score: 1

      Dear god I wish Mozilla would go back to long-term releases, or even just a six-month development cycle like Ubuntu.

    20. Re:FIrefox 8 Alpha... by hairyfeet · · Score: 2

      Gone are the days of anything making any sense in FF.

      FTFY.

      Seriously I have to wonder if someone from the IE or Chrome teams managed to plant a few ringers because frankly everything they've done lately has been to the advantage of Chrome and IE! Tossing point releases for a frankly insane 6 week release goal which killed everyone that was trying to roll FF into the enterprise (point for IE) and the constant changing of enough of the guts so that FF is a royal PITA to keep an extension going for which caused extensions for Chrome to shoot through the roof.

      I don't know, maybe its just me, but I can see only one of two reason why they would do this. One someone there wants the company to go tits up for some reason, so they are being the biggest dicks they can possibly be to run off the FF users and developers, or two they have become Netscape all over again, with a shitload of arrogance but without the code to back it up.

      Because lets face it folks the Chromium based stomp a mudhole in FF's ass. I've tried Chromium, Chrome, SWIron, QTWeb, and the one I now use and give customers Comodo Dragon, and frankly ALL of them stomp the shit out of FF in speed, responsiveness, and in conservation of CPU/RAM. The only thing FF had going for it was more extensions but FF is running those developers off as fast as they can! I just don't get it, it is like the company is trying to commit suicide.

      --
      ACs don't waste your time replying, your posts are never seen by me.
    21. Re:FIrefox 8 Alpha... by hedwards · · Score: 3, Informative

      And yet we also rail against people for still using IE6. Automatic updates for web exposed applications is a must.

      As for Firefox, it's not like they force you to update. There's a very convenient option under tools => options => advanced => update that modifies the behavior.

      As for bleeding edge, Firefox 6.0 is hardly bleeding edge. I get that some people don't want to be bleeding edge, but you must not know much about computers if you think that releases 4.0, 5.0 or 6.0 are bleeding edge.

    22. Re:FIrefox 8 Alpha... by archen · · Score: 1

      Why on such an old version? There's no reason because Firefox is FREE and it's not like they're making soul-sucking changes to the license lately.

      Firefox is moving to Chrome's release model. There are no more "versions" just the latest, best product they can make right NOW.

      Where I work we've adopted firefox, and we're stuck on 3.6. Every new version since 3.6 crashes on a report some people need to generate. If the "latest, best product they can make right NOW", doesn't address this before security fixes for 3.6 become a liability, the next upgrade of firefox will be to another browser.

    23. Re:FIrefox 8 Alpha... by arose · · Score: 1

      Furthermore, it lets them publish new features as they go because there is no expectation of perfect compatibility (and I say expectation, because things still broke) with everything sharing the same major version number over several years. This means that less development time is wasted on back- and forward-porting. Usable features get into web-developer hands, better browsers into user hands. People expecting Mozilla to be their private IT department are not as important as they think they are.

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    24. Re:FIrefox 8 Alpha... by Anonymous Coward · · Score: 0

      Why don't you just turn auto-update off and stop whinging?

    25. Re:FIrefox 8 Alpha... by Anonymous Coward · · Score: 0

      Plugins almost never break, but extensions often do. Sorry if I seem pedantic about it, but they are quite separate things, and both plugins and extensions are types of add-ons.

    26. Re:FIrefox 8 Alpha... by markjhood2003 · · Score: 1

      I downgraded to Firefox 3.6 because it's the most stable supported version. None of the other major versions get any security fixes unless you upgrade to the next major version. Firefox 4 and above simply don't work in the corporate environment.

    27. Re:FIrefox 8 Alpha... by markjhood2003 · · Score: 5, Informative

      3.6 is is the long-term release as far as I can tell. It still gets updates for security fixes. I just updated to 3.6.20 a few days ago.

    28. Re:FIrefox 8 Alpha... by MajinCline · · Score: 1

      I agree... I see no problem with the new version pipelining scheme, but there is no need to report what is happening in every single 'channel' of Firefox. If anything, pick one of them (perhaps the Release channel) and report the releases/new features in it.

    29. Re:FIrefox 8 Alpha... by jbeaupre · · Score: 1

      Coincidentally (or likely not), this is the longest my FF8a1 has gone without automatically updating. It's been 4 days. That's news!

      FWIW, it's the 64 bit version and has been running rather well. 64 bit flash too.

      --
      The world is made by those who show up for the job.
    30. Re:FIrefox 8 Alpha... by the+linux+geek · · Score: 1

      FF8 nightlies already exist.

    31. Re:FIrefox 8 Alpha... by mabhatter654 · · Score: 1

      Fix the report?

      While you're at it make the report cross browser, tidy, and validated to the latest DTD.

    32. Re:FIrefox 8 Alpha... by Anonymous Coward · · Score: 0

      I like what they are doing.

      Instead of every 2 years we get something that is about on par with the competition. We get new features as they are done. Those features may have taken 2 years to make. But do you want an additional 1.5 years for something just because 300 other features are not done yet? For example the JS stuff they added was basically done last September. We didnt see any of it until the end of feb. Because it was tied to a major big bang release.

      The actual version numbers matter little. Just that there IS one you can track to. That is all that is important. Many places i work I just use the internal subversion number for the version number.

      All you want to know is version A is better than B and that C is coming. And I have A right now. A date scheme is what Ubuntu uses. No one really bitches about that...

      Release early release often. That is the open source way...

    33. Re:FIrefox 8 Alpha... by perryizgr8 · · Score: 1

      i find 3.6 to be the latest version which still works reasonably even with ~40 tabs open.

      --
      Wealth is the gift that keeps on giving.
    34. Re:FIrefox 8 Alpha... by archen · · Score: 1

      It is cross browser, works in all other browsers - just not new versions of firefox.

      Many of us don't have the luxury of being able to fix these sorts of things in business.
      Really the report shouldn't even deal with a web browser but everyone is basically convinced it's firefox's fault since everything else works. Possibly true from that viewpoint.

    35. Re:FIrefox 8 Alpha... by sweatyboatman · · Score: 1

      seriously? ok, that is stupid.

      --
      It breaks my pluginses, my precious!
    36. Re:FIrefox 8 Alpha... by Anonymous Coward · · Score: 0

      A lot of other people could care less as well. That's why they are complaining.

    37. Re:FIrefox 8 Alpha... by Anonymous Coward · · Score: 0

      And I bet we'll again hear about how they "fixed" the memory leak issue that has plagued Firefox since at least version 2.5.

      It doesn't really matter anyhow. Firefox is old and irrelevant these days. I don't think I know a single person who still uses that antiquated pile of crap.

    38. Re:FIrefox 8 Alpha... by Anonymous Coward · · Score: 0

      I'm 90% sure that PPAs came after 8.04.

    39. Re:FIrefox 8 Alpha... by Anonymous Coward · · Score: 1

      ...Asa, is that you?

    40. Re:FIrefox 8 Alpha... by Darinbob · · Score: 1

      This is why I think Mozilla has given up being customer driven and is selfishly being developer driven. Ie, they do what is convenient for developers.

      You don't need to back-port features, you only need to back-port bug fixes. Not everyone needs these new useless features. If people want the new features than can upgrade. If they're happy with the current product then they should not be pressured to upgrade except to get patch releases for security. At least that's the way it should be if you care even a small amount for customers.

    41. Re:FIrefox 8 Alpha... by tidepool · · Score: 1

      Come December we will be celebrating Firefox 22. and sometime next year it will be Firefox 42 and we will be left looking for a question.

      I liked this post quite a bit. It was very mildly relevant, but I'm happy I was geeky enough to chuckle.

      Cheers,
      Bny

    42. Re:FIrefox 8 Alpha... by dissy · · Score: 1

      Next in few mins...Firefox 8 Alpha released and Firefox 9 Preview released

      Don't worry, the only difference between FireFox 8 and FireFox 24 will be six additional changelog entries :P

    43. Re:FIrefox 8 Alpha... by kangsterizer · · Score: 1

      Actually, we do report Chrome versions ;-)

    44. Re:FIrefox 8 Alpha... by piripiri · · Score: 1

      You can still add the repository and keys manually.

    45. Re:FIrefox 8 Alpha... by arose · · Score: 1

      This is why I think Mozilla has given up being customer driven and is selfishly being developer driven. Ie, they do what is convenient for developers.

      That is only the case if you position yourself as the target customer.

      You don't need to back-port features, you only need to back-port bug fixes.

      You need to back-port them if you are going if you are going to have any feature releases within a major release and base development on trunk. Otherwise you have to forward-port. The good

      Not everyone needs these new useless features.

      It seems that anyone who wants to capture all of Mozilla's customers is maintaining old Firefox releases. Good news, anyone is free to do it. Just get it from this new, customer driven entity that is bound to fill this huge hole in the market.

      If people want the new features than can upgrade.

      And if they don't, web developers should support them for eternity, just like they are planning to support IE6 for eternity.

      If they're happy with the current product then they should not be pressured to upgrade except to get patch releases for security.

      Does Microsoft pressuring people to upgrade from IE6 (or EOLing W2K) makes them not customer driven? Does Apple stopping support for the 3G make them not customer driven

      --
      Analogies don't equal equalities, they are merely somewhat analogous.
    46. Re:FIrefox 8 Alpha... by Anonymous Coward · · Score: 0

      No actually, I think he meant to say:

      "Gone are the days of... FF." ;)

    47. Re:FIrefox 8 Alpha... by JMJimmy · · Score: 2

      While you're absolutely correct I used the wrong word, but did it really need to be pointed out? You obviously understood and given the context of where the term was used, I think others could too. But you are 100% correct, I meant to use the term extensions.

    48. Re:FIrefox 8 Alpha... by HereIAmJH · · Score: 3, Insightful

      FF5 didn't upgrade to FF6 automatically on any of my machines.

      The only thing that stopped it on my Win7 laptop is the security message asking me if I wanted to allow the updater to change the system, every time I launched it. I kept telling it no, got tired of that and looked in Firefox and it told me it was a 5.x update. Let it install and suddenly I'm now running v6.x. As soon as I find a suitable replacement, I'm pulling it from all my systems. And I've been running it since Phoenix 0.3. I'm not amused. Some of us don't want to be bleeding edge.

      --
      Another day, another update to a Google android app.
    49. Re:FIrefox 8 Alpha... by Anonymous Coward · · Score: 0

      I upgraded to Firefox Aurora because every version I've ever used has been nothing but stable. I've used and recommended every released version (and test pre-release versions) of Firefox in a corporate environment without issue. You know what they say about opinions.

    50. Re:FIrefox 8 Alpha... by Anonymus · · Score: 1

      Here's the tl;dr version of that bug report: Techies should no longer suggest Firefox to their friends and relatives and should start installing Chrome, Opera, or Safari instead. The Mozilla devs have completely gone off the deep end, in case that wasn't already apparent to anyone for the last year or two.

    51. Re:FIrefox 8 Alpha... by DaVince21 · · Score: 1

      Really? I've seen a few "Chrome version ... released" articles on /. ...

      --
      I am not devoid of humor.
    52. Re:FIrefox 8 Alpha... by NotBorg · · Score: 1

      Wrong. It is up to the developers. If you don't like it then become a developer and exercise your freedom.

      I do not understand how you feel so strongly entitled to have software developed to YOUR expectations. Especially when it is something you DO NOT CONTRIBUTE TO IN ANY WAY. Do you pay for it? Do you beta test in a meaningful way? Do you do anything but bitch about it on Slashdot? Why are you entitled to have it your way? Who made you god of Mozilla?

      Justify your entitlement.

      I said in a previous Fx story

      And as you will continue to say EVERY SINGLE TIME there is an article about Firefox. Even if it has nothing to do with the article. For this you'll be moderated "Insightful" rather than "Troll." I don't even have to scroll down... I know there's another "Insightful" posting about how bad Firefox leaks memory. Bringing every defect, be it real or perceived, every time someone says ANYTHING about Firefox is "Insightful" not "Redundant", "Troll", or "Off topic."

      --
      I want this account deleted.
    53. Re:FIrefox 8 Alpha... by arglebargle_xiv · · Score: 1

      Next in few mins...Firefox 8 Alpha released and Firefox 9 Preview released... Do we need to clog up the front page with these articles? Gone are the days of version numbers making any sense in FF. We don't report Chrome versions do we?

      Shh, not so loud! They're not supposed to know that the Firefox development process switched to:

      while( TRUE )
      {
      cat /dev/urandom > firefox.xul;
      version++;
      }

      after 3.6.

    54. Re:FIrefox 8 Alpha... by Anonymous Coward · · Score: 0

      Chrome also doesn't pop up update screens and shove the version numbers in your face when you're just trying to open the browser and use it.

  2. Aw c'mon by AndyAndyAndyAndy · · Score: 2

    As a web designer, they're turning my hair white with all these versions. Not so much that we need worry about things becoming incompatible, etc. but it's spreading out the userbase, which is just inherently more difficult to ensure cross-version identicality.

    --
    It's always confirmation bias!
    1. Re:Aw c'mon by empiricistrob · · Score: 1

      I agree that it's annoying, but in practice I don't think this causes any compatibility issues. Before did you worry separately about whether you support 3.5, 3.5.1, ..., 3.6,3.6.1, etc? Probably not. Now you should probably just think of FF4-7 as being essentially the same version until you find out otherwise (just as you likely did previously with the minor version numbers).

    2. Re:Aw c'mon by AndyAndyAndyAndy · · Score: 1

      Yeah, pretty much. I don't expect anything to happen, but it's a lot of changes that bring some percentage of the prior userbase along to the new version. Now we'll have more people spread out among version numbers (albeit arbritrary). It's happening fast enough that a security mistake in one of the many versions gone by between then and now could pop up eventually, meaning we need to (for example) tailor our scripts around one of them.

      But again, yeah I hear ya, probably nothing to actually be concerned about.

      --
      It's always confirmation bias!
    3. Re:Aw c'mon by Baloroth · · Score: 4, Insightful

      Yeah, but the point was you knew right away 3.6 was nearly identical to 3.6.1 (well, should be anyways) and was probably pretty similar to 3.5, but not to 4.0. Now, you have no clue if 7 represents a major change or just a bugfix without actually testing it. Hence, frustration for developers. Mozilla is basically giving them less information about what the release cycles contain, and for no good reason whatsoever. And that is why people complain.

      --
      "None can love freedom heartily, but good men; the rest love not freedom, but license." --John Milton
    4. Re:Aw c'mon by Anonymous Coward · · Score: 0

      Why do "web designers" insist on "identicality"? I don't give a damn what exact spacing or font you chose; just serve me the content and let my browser render it how I choose.

    5. Re:Aw c'mon by AndyAndyAndyAndy · · Score: 2

      Because companies that pay us to do these things care an awful lot about how their site looks to the most amount of people. Then again, they hire people for "SEO," so it's not like they know what they're talking about. But who's going to tell them that?

      --
      It's always confirmation bias!
    6. Re:Aw c'mon by Anonymous Coward · · Score: 1

      Um... I build web apps for a living.... that's what I do day in and day out.... FF's version changes have barely affected what I do. Frankly, if you're doing it right in the first place, this should pretty much be a non-issue.

    7. Re:Aw c'mon by Anonymous Coward · · Score: 0

      If only they had release notes and a product roadmap to document changes...

    8. Re:Aw c'mon by JMJimmy · · Score: 1

      Agreed. Rendering engine changes are what to look out for and even at that I run everything through a check to make sure the feature I'm accessing actually exists before using it. Sure it costs a bit in speed but rarely does anything break. If it does break, it's usually because the error handling needs to be tweaked for when a feature doesn't exist and a hack is used as a backup.

    9. Re:Aw c'mon by Kippesoep · · Score: 1

      Now, you have no clue if 7 represents a major change or just a bugfix without actually testing it.

      Really? What about 5.0.1 and 4.0.1? Bugfix releases still can and do happen. 7 is a feature release, as were 6, 5 and 4 before it. Perhaps the features added aren't alway major news or huge visible changes, I agree. But at least they're coming available much quicker now and can be refined sooner as well.

      Hence, frustration for developers.

      As a web developer, I am not frustrated by the jump in version numbers. It is, after all, just a number. If anything, it makes it easier to know when new functionality becomes available, even if it comes in bite-sized chunks, rather than wondering whether a point release is just a collection of bugfixes or actually expands functionality. If anything, I thought that they shouldn't have done the out-of-process plugins in the small numerical step from 3.6.3 to 3.6.4... that alone warranted calling it 3.7, imho.

    10. Re:Aw c'mon by Joce640k · · Score: 1

      As a web designer, they're turning my hair white with all these versions.

      Um, you're much more likely to have everybody using the same version now they've added auto-update...

      --
      No sig today...
    11. Re:Aw c'mon by iridium213 · · Score: 1

      Quicktime plugin w/ embedded streaming was broken thanks to the unsolicited Firefox 6 'security' upgrade. First week of classes and lecture videos stop working. Thanks Mozilla. Now we have one more reason to recommend Chrome or Safari..

    12. Re:Aw c'mon by Reapman · · Score: 1

      Does Chrome keep you up all night too?

      Maybe if you were a plugin developer I'd be concerned, but the way you have to think about these version numbers is to move the decimal point to the left. This isn't a whole new version how coders think of it, it's really just a point release - it's like getting stressed out because Firefox released 3.6 after 3.5 (or whatever was before 3.6). It's practically a non issue.

      It's not how I'd run the show but really people need to stop whining about these version numbers breaking zomgeverything. Firefox 7 will, from all accounts I've seen, render your web page EXACTLY THE SAME.

      90% of users will just get an autoupdated new version anyways.

    13. Re:Aw c'mon by Merk42 · · Score: 1

      For the tens of thousands of visitor to the webpages I work on, Firefox 6 usage has already surpassed Firefox 5 usage. I'm sure by the end of the weekend FF4 and FF5 will be a drop in the bucket.

    14. Re:Aw c'mon by g13n · · Score: 1

      As a web designer, they're turning my hair white with all these versions. Not so much that we need worry about things becoming incompatible, etc. but it's spreading out the userbase, which is just inherently more difficult to ensure cross-version identicality.

      If I were you, I would just rely on the YUI Graded Browser chart [yuilibrary.com/yui/docs/tutorials/gbs/] and develop against it, any way there's hardly any difference between these 6, 7, 8, ... versions ;-)

    15. Re:Aw c'mon by NatasRevol · · Score: 1

      CaMel notation would make that so much better.

      --
      There are two types of people in the world: Those who crave closure
    16. Re:Aw c'mon by cachimaster · · Score: 3, Interesting

      I think that's the idea, to stop developers from relying on version # and start coding to standards.

    17. Re:Aw c'mon by Anonymous Coward · · Score: 0

      As a web developer, I am not frustrated by the jump in version numbers. It is, after all, just a number. If anything, it makes it easier to know when new functionality becomes available, even if it comes in bite-sized chunks, rather than wondering whether a point release is just a collection of bugfixes or actually expands functionality. If anything, I thought that they shouldn't have done the out-of-process plugins in the small numerical step from 3.6.3 to 3.6.4... that alone warranted calling it 3.7, imho.

      The irony of your post is delicious.

    18. Re:Aw c'mon by Anonymous Coward · · Score: 0

      No kidding. Is this a major release? A minor release? Is it worth upgrading? Or should I wait another 6-12- or 18 weeks?

      The major.minor version designation has worked fine for decades, but along comes some yahoo at mozilla who decides that using integers will convey more information. Now you have no idea how close version 7 is to 5 or even 6. This, combined with stupid design decisions like getting rid of the status bar (is saving 10 pixels on a screen with 1200 vertical dots going to increase anyone's productivity?) makes me wonder if they are deliberately trying to sabotage Firefox.

      I think the guy at Apple who reversed scrolling in OSX Lemon..err...Lion must be making the decisions at Mozilla.

    19. Re:Aw c'mon by BenoitRen · · Score: 1

      7 is a feature release, as were 6, 5 and 4 before it.

      Firefox 4.0 was not a feature release. It was a major release that included changes in the core.

      If anything, I thought that they shouldn't have done the out-of-process plugins in the small numerical step from 3.6.3 to 3.6.4... that alone warranted calling it 3.7, imho.

      You just showed that version numbers aren't just a number but carry meaning with them. Mozilla using them arbitrarily distorts their meaning, and this is what people are complaining about.

    20. Re:Aw c'mon by Anonymous Coward · · Score: 0

      Then what metric do we use to know WHEN to check compatibility?

    21. Re:Aw c'mon by Anonymous Coward · · Score: 0

      Can I get a sample site please?

    22. Re:Aw c'mon by Jah-Wren+Ryel · · Score: 1

      Because companies that pay us to do these things care an awful lot about how their site looks to the most amount of people. Then again, they hire people for "SEO," so it's not like they know what they're talking about. But who's going to tell them that?

      Sounds to me like you are arguing yourself out of a business opportunity. If FF's rapid update schedule is a problem (or even if it isn't but your clients think it is) then that means more billable hours for you - hours that you don't even have to take the blame for screwing up, it's all Mozilla's "fault."

      --
      When information is power, privacy is freedom.
    23. Re:Aw c'mon by Kippesoep · · Score: 1

      Firefox 4.0 was not a feature release. It was a major release that included changes in the core.

      Yet another arbitrary distinction... especially when most people here complain that 4.0 should actually be called 3.7.

      You just showed that version numbers aren't just a number but carry meaning with them. Mozilla using them arbitrarily distorts their meaning, and this is what people are complaining about.

      They don't carry meaning other than what we assign to them. What I showed is that they broke their own rules before, in a small way, pointing out the inconsistency does not mean that I think those "rules" are important. Are they doing it arbitrarily now? Nope, just differently. Bugfixes etc: small number, features added and major functionality changes: first number. It's not confusing to me, nor is the old system. And I don't care if a user says he has a problem on 4.3.5 or 7.0. The only thing that I find annoying about the change in version numbers is the addons needlessly expiring, but that situation already seems to be improving. How those numbers increase isn't very important, as long as we have an easy way of determining which is which. Their removing the number from the about box does have me worried though.

    24. Re:Aw c'mon by Anonymous Coward · · Score: 0

      as a "web designer" i would hope you would use feature detection with graceful fallbacks ... never version detection

    25. Re:Aw c'mon by BenoitRen · · Score: 1

      Bugfixes etc: small number, features added and major functionality changes: first number. It's not confusing to me, nor is the old system.

      The problem is that bugfix releases and security updates are now also first number changes. There's no way for web developers to know when the core that does the parsing and rendering changed any more.

    26. Re:Aw c'mon by Fallingcow · · Score: 1

      We'll just have to memorize "4, 15, 25, and 28 are major versions with large differences, 12, 18, and 26 would have been major point releases and break or fix X, Y, and Z, respectively".

      Fuck this new numbering scheme.

    27. Re:Aw c'mon by Anonymous Coward · · Score: 0

      Not really. I can run most pages fine in Firefox 4 and they'll work in Firefox 5, 6 and 7 without any issues. They've pretty much got most standards implemented, the newer standards that are in draft will be in the later version and they mostly do optimizations so Firefox runs faster.

      Unlike Internet Explorer, which until IE9 doesn't seem to support very much at all.

    28. Re:Aw c'mon by Anonymous Coward · · Score: 0

      I'm running version 3.6.18, like a boss. I guess, by now, it's the equivalent of running the Windows ME version of Firefox, or something.

    29. Re:Aw c'mon by Anonymous Coward · · Score: 1

      I think that's the idea, to stop developers from relying on version # and start coding to standards.

      Call me when all browsers implement the entirety of a standard (none), implement all of it correctly (none) and, if they don't implement all of it (all of them), that they don't implement disjoint sets of features (all of them, except Chrome/Safari/WebKit which are the same as each other but not as Opera or Firefox or Internet Explorer).

    30. Re:Aw c'mon by Anonymous Coward · · Score: 0

      Yeah, but the point was you knew right away 3.6 was nearly identical to 3.6.1 (well, should be anyways) and was probably pretty similar to 3.5, but not to 4.0. Now, you have no clue if 7 represents a major change or just a bugfix without actually testing it.

      Well, here's your answer:

      There will never be a major change ever again. It's all incremental changes and evolution from here on in.

      Sorry to make it so easy for you...

    31. Re:Aw c'mon by Anonymous Coward · · Score: 1

      And I'm sure as soon as browsers all render the same standard-compliant code identically, developers will happily do so.

      In the meantime, we have to work to several creative interpretations of how code should be rendered, and why we need to know when $Browser_vendor_of choice is about to re-write a lot of its code.

  3. Memory Reporting by MozeeToby · · Score: 3, Interesting

    Not in the summary is an opt in feature that will report your memory use (presumably along with what pages you are on and extentions you are using) back to Mozilla so they can finally put the "but FF using 2 GB of RAM on my machine" bugs to rest, either by fixing them or by dispelling the myth depending on which is the case.

    1. Re:Memory Reporting by arth1 · · Score: 1

      Not in the summary is an opt in feature that will report your memory use (presumably along with what pages you are on and extentions you are using) back to Mozilla so they can finally put the "but FF using 2 GB of RAM on my machine" bugs to rest, either by fixing them or by dispelling the myth depending on which is the case.

      More likely is that they'll continue current practice, and refuse to even look at the bug for anyone who has any plugin installed, and instead assume that it must be the plugins that are at fault.

    2. Re:Memory Reporting by Anonymous Coward · · Score: 0

      It only takes me 3-4 days of typical use to get firefox to the point. If need be, I think I could tolerate 3-4 days without plugins just to make a point.

    3. Re:Memory Reporting by Anonymous Coward · · Score: 0

      That's no longer current practice; there's a number of filed bugs where extensions and plugins are responsible for the memory leaks, and the Mozilla guys have been contacting the developers and helping them track down the leaks.

      An example.

    4. Re:Memory Reporting by arth1 · · Score: 1

      This is good news.

    5. Re:Memory Reporting by kangsterizer · · Score: 1

      Mod parent up. ;-)

  4. Fix the leaks perhaps?? by mehrotra.akash · · Score: 1

    "The JavaScript garbage collector works more frequently to free up memory and improve performance when you have many tabs open or keep Firefox running for a long time."

    Shouldnt the leaks be fixed, rather than having a garbage collector cleaning them up?

    Isnt it like putting a bigger engine on a car with square wheels instead of making the wheels round?

    1. Re:Fix the leaks perhaps?? by siride · · Score: 1

      It would be fixed by using a non-GC language. Seeing how JavaScript has become the defacto scripting language of the client-side web, I doubt this is going to change any time soon.

    2. Re:Fix the leaks perhaps?? by H0p313ss · · Score: 1, Troll

      Shouldnt the leaks be fixed, rather than having a garbage collector cleaning them up?

      You sir just won Slashdot's "Wannabe techie dumb comment of the day."

      --
      XML is a known as a key material required to create SMD: Software of Mass Destruction
    3. Re:Fix the leaks perhaps?? by recoiledsnake · · Score: 4, Insightful

      If the garbage collected collected leaks, they wouldn't be called leaks anymore.

      --
      This space for rent.
    4. Re:Fix the leaks perhaps?? by arth1 · · Score: 1

      Shouldnt the leaks be fixed, rather than having a garbage collector cleaning them up?

      Welcome to the age of managed code. No, what you do is of course add another abstraction layer to distance yourself from the bugs, and add unit tests for the purpose of validating your code (instead of finding something wrong with it, which once upon a time was the purpose of tests).

    5. Re:Fix the leaks perhaps?? by HarrySquatter · · Score: 2

      and add unit tests for the purpose of validating your code (instead of finding something wrong with it, which once upon a time was the purpose of tests).

      Anyone doing unit tests properly is both validating their code and finding something wrong with it. If you're tests don't do both, you're doing it wrong.

    6. Re:Fix the leaks perhaps?? by Anonymous Coward · · Score: 0

      Why use a scripting language at all, eh Grandpa?

    7. Re:Fix the leaks perhaps?? by Darinbob · · Score: 1

      The vast majority of scripting languages depend upon garbage collection. Possibly naive garbage collection like reference counting but it's there. This is in the nature of a high level language. These are not new things they've been around over fifty years.

    8. Re:Fix the leaks perhaps?? by siride · · Score: 1

      I know...

      The OP seemed to think that the problem was the existence of the GC, rather than its tuning. To "fix" that would require switching to a non-GC high-level scripting language (an absurd proposition, of course).

    9. Re:Fix the leaks perhaps?? by Anonymous Coward · · Score: 0

      That is like saying "If I don't find something wrong with my working and bug free code then I'm not testing it right."

      Really do you even know what a unit test is? It's supposed to find problems with the unit being tested. Unit tests won't find algorithmic problems or problems with the entire program. And they only find what you expect them to find, even if you do a unit test properly you can miss bugs, and conversely you can find non-existent bugs in your code if you do unit testing wrong. Mr. Squatter have you ever done unit testing or are you just trying to sound smart like Andy?

    10. Re:Fix the leaks perhaps?? by Anonymous Coward · · Score: 0

      My unit tests are always properly done, and they validate three things: that I am super-smart, that my code is bug-free and that it is everyone else's fault.

    11. Re:Fix the leaks perhaps?? by The+Dawn+Of+Time · · Score: 1

      Welcome to Slashdot. The population used to be pretty good at understanding how these sorts of things worked, but the new style seems to be "shit on everything in a manner that clearly demonstrates to anyone who actually knows something about what I'm shitting on that I actually know nothing."

  5. Mozilla version numbering system by Anonymous Coward · · Score: 0

    Is that considered a bug or a feature?

  6. Really? What's the point of this version numbering by nhat11 · · Score: 0

    If the releases are that close together, just keep it in development until they get in all the bugs and features in. No one likes to upgrade every month.

  7. enough already with the version bloat! by datapharmer · · Score: 0

    Really? The beta for 7 comes out the same week as 6 is released? This version nonsense has got to stop. You know those periods are there for a reason... Hint: Big number for major changes that might affect reverse compatibility, 1st decimal for minor changes, 2nd decimal for bug fixes

    --
    Get a web developer
    1. Re:enough already with the version bloat! by kakyoin01 · · Score: 1

      They are already working to remove the version numbering, whether it's for better or for worse.

      --
      The more you know, the more you have to say and the more you should listen.
    2. Re:enough already with the version bloat! by Millennium · · Score: 5, Insightful

      It's more that the beta for 7 comes out pretty much the instant 6 is released. One of the more interesting aspects of the Mozilla development process is that they essentially have a pipeline of four "releases" going on at once: Current (stable stuff, now 6), Beta (code being stabilized, now 7), Aurora (testing and major bugfixes, now 8) and Nightly (new feature work, now 9). When it comes time to do a new release, Current gets booted out, Beta and Aurora get promoted, and Nightly coughs up a build that becomes the new Aurora. It would actually be a pretty good system, except for the part where they forgot about maintenance releases and long-term support.

    3. Re:enough already with the version bloat! by hesaigo999ca · · Score: 0

      I agree, at this point i think it a game on all their parts to force us to stop putting faith in version numbers, and just blindly keep getting the updates ...aka..latest version....

      This to me is such a fail, as most web devs need to be sure of the versions they are compatible with...and this will just make it impossible to tell...

    4. Re:enough already with the version bloat! by Anonymous Coward · · Score: 0

      At least once they remove the version numbering, we won't have to put up with a new release announcement every week.

    5. Re:enough already with the version bloat! by mabhatter654 · · Score: 1

      Write to the HTML5 spec, validate, and don't worry about the other stuff. HTML was never designed to be "pixel perfect". That's a limitation that has been in the first page of the spec manual since forever.

    6. Re:enough already with the version bloat! by Anonymous Coward · · Score: 0

      Perhaps first you should read up on the Firefox release cycle. When a new version is released, the beta is incremented by one. This isn't random or a coincidence.

    7. Re:enough already with the version bloat! by tepples · · Score: 1

      Write to the HTML5 spec

      I agree with you as for web pages. But write Firefox add-ons to what spec?

      HTML was never designed to be "pixel perfect".

      It also wasn't designed to look completely unusable when a user's web browser supports only half of the CSS selectors and properties that your page uses, was it?

    8. Re:enough already with the version bloat! by asa · · Score: 1

      "I agree with you as for web pages. But write Firefox add-ons to what spec?"

      The Add-ons SDK. Write to that and your add-ons won't break with updates. https://addons.mozilla.org/en-US/developers/builder Yeah. It's that easy. Write to the stable APIs of the Web and the stable APIs of Firefox. When you do that, things shouldn't break and when they do, they're very rare and can be pinned on Firefox as legitimate bugs.

    9. Re:enough already with the version bloat! by max · · Score: 2, Insightful

      This to me is such a fail, as most web devs need to be sure of the versions they are compatible with...

      No, the "fail" is in that very chain of thought. Those web devs should not call themselves web devs since they do not understand the fundamental differences between the old media they used to work with and the new media, having to resort to web browser version to achieve what they foolishly are striving for.

      At first I was not too keen on version number inflation, but thinking about it I couldn't care less. Actually, I find it good if it rids the world of people targeting web browser versions when they develop for the web. Target standards, not web browsers.

      The only problem as I see is the plugins. That could be handled if Mozilla decided to create a stable API for plugin development and have version numbers on that API instead. This could even create a more stable browser with less unpredictability when multiple plugins are used. Another way, although more anarchistic, is to create a crowd sourced database of version compatibility between browsers and plugins, not having installers contain that information, but rather let us (the users) try it out and report.

    10. Re:enough already with the version bloat! by tepples · · Score: 1

      Are there things that add-ons commonly do with the old (pre-Jetpack) APIs of Firefox that are not possible with the stable APIs of Firefox?

    11. Re:enough already with the version bloat! by hesaigo999ca · · Score: 1

      >plugin development and have version numbers on that API instead.
      Same issue dude, we need to know a version number, and might have to do something diff. because of it, how is that any different then say needing to know if ie6 to avoid using a special jquery call or structure that hangs the system???

  8. Re:Really? What's the point of this version number by sakdoctor · · Score: 1

    Or even better, a rolling release.

  9. It starting to be funny by IgnitusBoyone · · Score: 1

    We might as well link the third article on Slashdot to an RSS feed or Mozilla releases. Its starting to get an article every 5 days or so.

    --
    Momento Mori
  10. Sorry but you're too late by Ossifer · · Score: 4, Funny

    Firefox 7.0 has already reached end-of-life at the time of this posting...

    1. Re:Sorry but you're too late by sakdoctor · · Score: 3

      Ah sorry, that joke reached EOL when firefox 5 was released.

    2. Re:Sorry but you're too late by Hellasboy · · Score: 1

      Sorry. But in Korea, Firefox 7.0 is already only for old people...

      --

      "Tread softly because you tread on my dreams"
    3. Re:Sorry but you're too late by alostpacket · · Score: 1

      I thought they EOL'd it when the 90's called...

      --
      PocketPermissions Android Permission Guide
  11. Radical idea: Fix the plugin api! by ilsaloving · · Score: 0

    I have an idea... how about stabilizing the plugin API so that all my plugins don't break with every single bloody release? I always thought Apple was bad regarding forced obsolescence , but Mozilla now makes Apple look like a granite pillar of stability.

    Chrome pumps out releases like there is no tomorrow, yet they don't seem to have this problem. Heck, Chrome could have updated this morning, and I wouldn't have even noticed.

    I already have enough to do without having to worry about my browser setup getting mangled every couple of weeks.

  12. I'm beta testing... by Anonymous Coward · · Score: 0, Funny

    I'm posting this from Firefox 120945324-alpha-beta-pi-release-42.

    This version seems stable... oops - not any more. I took too many seconds to type this.

  13. Can I just say this? by erroneus · · Score: 0

    I have an aversion to this versioning?

    1. Re:Can I just say this? by mulvane · · Score: 1

      I keep a version of aversion in subversion.

  14. Firefox 7! 8! 9! by Anonymous Coward · · Score: 0

    The version number inflation with Firefox doesn't bother me at all, because I don't use Firefox anymore.

  15. Master race reporting in. by Anonymous Coward · · Score: 0

    >2011
    >Not using Nightly 9.0 master race.

  16. minimum tab width by Anonymous Coward · · Score: 0

    Are they going to fix the minimum tab width? I can type about:config,, but I use chrome instead of trying to learn enough about xml to figure out how to fix the config file to adjust the minimum tab width. Still very disappointed that the FF team made FF less usable than IE.

    1. Re:minimum tab width by Anonymous Coward · · Score: 0

      Are they going to fix the minimum tab width? I can type about:config,, but I use chrome instead of trying to learn enough about xml to figure out how to fix the config file to adjust the minimum tab width. Still very disappointed that the FF team made FF less usable than IE.

      For 3.6.x, I use the following tweaks. Are these still available in 7.0? I got off the Fx "upgrade" train with 4.0. What did they fuck up this time?

      browser.tabs.tabMinWidth 0 # Yes, I really *do* want 30+ tiny square tabs. browser.tabs.closebuttons 3 # ...and one close button that doesn't move

      I use closebuttons=3 not just so that I can hover a mouse cursor over a static "X" icon and just click (because that's what ^W is for), but because I really *do* want 30+ tiny square tabs when I'm waist-deep in some forum with forced pagination. The less horizontal space taken up by the tabs, the better.

      And because I prefer to use tabs like a stack, not a thread, I also go with:

      browser.tabs.selectOwnerOnClose false browser.tabs.insertRelatedAfterCurrent false

  17. Whats the point... by Anonymous Coward · · Score: 0

    I've said this since version 3.

    Firefox 1.0 was great but it was built upon a horrible engine among other things. (Comparing it to Opera at the time)

    We are now at Version 7, not much has changed, they are basically polishing a turd unfortunately.

    They should have scraped Firefox at version 3 and started new, they know how to make some great features but they seem to spend their entire dev time on fixing firefox performance issues.

  18. Re:Inb4 autism by Anonymous Coward · · Score: 0

    We see you trollin', we hatin'
    Tryin to catch you postin' dirty

  19. make the update notifications more annoying please by Anonymous Coward · · Score: 2, Insightful

    It used to be a tiny little box that would slide up in the corner of the screen. It would stay there for exactly as long as it took for your brain to register the presence of the link, and then slide away. Unless you were a ninja and/or sniper you had no hope of hitting the link.

    Now a big, huge window flops up onto the middle of the screen WHILE I'M WATCHING A GODDAMN VIDEO. Half an acre of gray emptiness with two buttons and a line of text about the new version.

    I hope with future versions that the entire screen will be blacked-out, mariachi music will begin to play in the background along with the sound of 5 or 6 crying babies, and a 5 minute marketing video plays while the new version downloads and installs. Oh! And I hope they start forcing the icon onto the desktop with each update, Adobe style; that would rock.

  20. Anger at version number games. by Zombie+Ryushu · · Score: 1

    What was called FireFox 4.0 should have been called FireFox 3.7, and we should still be in 3.7.x phase. These version number games make me have the very real inclination to punch the people responsible in the face repeatedly. They are doing no less than turning FireFox, which once had reverence, into an object of ridicule.

    1. Re:Anger at version number games. by Anonymous Coward · · Score: 0

      Er ... really? Firefox 4 was a *major* update from 3.6. It added tons of new features and performance changes (I'm hesitant to say "improvements" because that doesn't seem to be the case for most people). It made total sense to call it Firefox 4, as it was easily as much a change from 3.6 as version 3 was from 2.

      It's version 5 that, according to the old numbering scheme, should really be something like 4.1. But now that they've changed their numbering scheme, it makes sense to call it Firefox 5. Because Mozilla is the developer, and they can number their products however they'd like.

      By the way, it's not called FireFox. It's Firefox.

    2. Re:Anger at version number games. by Anonymous Coward · · Score: 0

      They'll stop when they catch up with IE. Firefox 3.7 sounds a lot older than IE9. They are blowing through version numbers so they can catch up. Then, magically, I expect the version games to stop and we'll see FireFox 9.1.X

    3. Re:Anger at version number games. by Anonymous Coward · · Score: 0
    4. Re:Anger at version number games. by RebelWithoutAClue · · Score: 1

      Only until IE10 is announced.

      --
      "However beautiful the strategy, you should occasionally look at the results" - Winston Churchill
    5. Re:Anger at version number games. by Anonymous Coward · · Score: 0

      What was called FireFox 4.0 should have been called FireFox 3.7, and we should still be in 3.7.x phase. These version number games make me have the very real inclination to punch the people responsible in the face repeatedly.

      They should call it Firefox 420 because someone was on drugs to think this version numbering makes sense. And if you used it you'd be less included to punch people in the face, thought you might get the munchies.

  21. Re:Really? What's the point of this version number by arth1 · · Score: 2

    If the releases are that close together, just keep it in development until they get in all the bugs and features in. No one likes to upgrade every month.

    Speaking only for myself, I only like to upgrade when there (a) are compelling reasons, and (b) it's feasible.
    I use a plugin which is security related and thus signed, and there will never be a new version available at the day of the launch. If there isn't a new version before the next release, it means that in order to upgrade, I will have to hunt down the new version in archives, and install it that way.
    With other companies having release cycles of 6 months or a year, there's no way they can keep up with Firefox. So Asa D. has pretty much forced many of us to look elsewhere.

    Yes, I see the upgrade popup for Firefox, but I have to ignore it because upgrading will break my plugins. It's only a source of irritation.
    The supported distro I am on is at version 3.6.18, and there is no newer version. So why do I get the irritating pop-up at all?
    In Windows (in a VM), I am at FF5, and get a pop-up telling me that I should go to version 6. Sorry, I can't, until the plugins I need are signed for FF6. So why do I get a pop-up? Just to irritate me?

    I'm using other browsers more and more now, because the direction Mozilla is going in now is best described as the direction of the divine wind. Sorry, I don't plan to be aboard.

  22. They're ALL Betas by Jonathan+C.+Patschke · · Score: 5, Informative

    From the big Bugzilla thread about version numbers earlier this week:

    Users cannot sit on Firefox 4.x They will be updated to the latest version when they open the About dialog (or sooner) because all* but the current Firefox release are unsupported versions in the new rapid release cycle. Those not current versions do not not get critical security updates except via the current version. Firefox users will not be spread across Firefox 4, 5, 6, etc. They will be on the latest version or they will be about to be on the latest version.

    Effective expiration, lack of bugfixes, and rapidly replaced by newer versions with bugfixes? By any practical definition, there is no stable version. They're all betas from here onwards. The whole notion of a release isn't that it's bug-free, but that it's supported for a reasonably-long period of time.

    --
    Pining for the days when The Glorious MEEPT!!! graced SlapDash with his wisdom.
    1. Re:They're ALL Betas by Darinbob · · Score: 1

      They say "cannot sit on Firefox 4.x" like it's some universal law or something. Are they going to send goons out to my house to forcibly click the upgrade button? As opposed to having goons write popups that remind me to upgrade daily.

      Basically I'm just waiting for adblock to be supported on a browser other than chrome or firefox, or else I may just give up on the whole web thing as being fundamentally too broken to use.

    2. Re:They're ALL Betas by Anonymous Coward · · Score: 0

      I cannot disprove you... (mainly because you cannot prove yourself in the first place),
      but I think they might be *trying* to do something like this: http://www.youtube.com/watch?v=i7pkyDUX5uM
      Which is a good idea... as long as it really means âoealways stable. all the time. every snapshot!"

      But if there is a most wrong way to do this, Mozilla's take might well be it.

    3. Re:They're ALL Betas by Kalten · · Score: 1

      How much do you want to bet that sometime in the very near future, under Tools | Options (yes, I still use the menus, f*** off), under Advanced, the Update tab will vanish, and all meaningful ability to control Firefox updates will vanish?

      If Firefox had had some actual innovative ideas recently, I wouldn't (necessarily) have a problem, but they seem to have been copying Opera and especially Chrome, without actually thinking about WHY Opera and Chrome did what they did. Cargo cult, anyone?

    4. Re:They're ALL Betas by jalefkowit · · Score: 1

      They say "cannot sit on Firefox 4.x" like it's some universal law or something. Are they going to send goons out to my house to forcibly click the upgrade button?

      No, they're going to stop requiring a "click of the upgrade button" at all. When you launch Firefox it will silently update to the latest version automatically, no user intervention (or goons) required.

  23. Re:Whinedot - News For Complainers Stuff That Anno by HarrySquatter · · Score: 2

    So what if it's free. How does that make it above criticism? That's got to be one of the lamest excuses for trying to stifle criticism of something. If you're just going to whine and complain when your users complain about stuff, then why even release something for users anyway? Why not just keep it as some internal tool so the devs can circle jerk in peace? That seems to be what Mozilla wants now.

  24. 6.0 reporting here by equex · · Score: 2

    My FireFox has updated itself to 6.0 now and my humble plugin-requirements still work. I use NoScript, AdBlock+, BetterPrivacy and DownloadHelper. So you will at least be able to surf the web with reasonable security. As soon as the plugins starts breaking, I'm going straight for Chrome. I don't know much about Chrome these days, I last used it 3 years ago. How is the stance with plugins on Chrome now ? If there are still no plugins, do you at least have the equivalent functions of the plugins i mentioned above?

    --
    Can I light a sig ?
    1. Re:6.0 reporting here by Tridus · · Score: 1

      Chrome's addins don't break because they have much less access to the browser then FF extensions (which can use internal APIs and that's why they break more often). For example there's no true equivalent to FlashBlock on Chrome because the API makes it impossible. The closest thing just hides Flash, but it's still running.

      --
      -- "So they told me that using the download page to download something was not something they anticipated." - Bill Gates
    2. Re:6.0 reporting here by perryizgr8 · · Score: 1

      in chrome for blocking flash and stuff like that there's a built in feature. go to about:flags and enable click2play. then enable it in the plugin settings. it works exactly like flashblock!

      --
      Wealth is the gift that keeps on giving.
    3. Re:6.0 reporting here by vlueboy · · Score: 1

      in chrome for blocking flash and stuff like that there's a built in feature. go to about:flags and enable click2play. then enable it in the plugin settings. it works exactly like flashblock!

      Thank you very much. Knowing this flags page exists and enables GPU rendering and other nifty stuff is a nice weekend gift. Carry on, kind sir!

  25. Re:Radical idea: Fix the plugin api! by Anonymous Coward · · Score: 0

    You don't mean plugins; you mean extensions.

  26. Who put the 'fox' in Firefox? by macraig · · Score: 1

    Next up: Mozilla becomes a wholly owned subsidiary of the Fox News empire after Google and other funding sources dry up.

    1. Re:Who put the 'fox' in Firefox? by afabbro · · Score: 1

      Next up: Mozilla becomes a wholly owned subsidiary of the Fox News empire after Google and other funding sources dry up.

      I love that pseudorumor so much I am going to start spreading it.

      --
      Advice: on VPS providers
    2. Re:Who put the 'fox' in Firefox? by macraig · · Score: 1

      Spread the Fox! They'll have a new Web site up shortly: spreadthefox.com.

  27. Re:Really? What's the point of this version number by denis-The-menace · · Score: 3, Informative

    You could use the super-secret Mozilla Add-on SDK

    QUOTE: help ensure your add-on continues to work as new versions of Firefox are released.

    Nobody seems to be mentioning this solution. Not even Mozilla.

    --
    Obama's legacy: (N)othing (S)ecure (A)nywhere and (T)error (S)imulation (A)dministration
  28. performance enhancements? by waddgodd · · Score: 1

    Okay, so Major versions mean "new feature that may be buggy, so avoid .0 releases", Minor versions mean "okay, no new features, let's just concentrate on enhancing performance and security of the features we do have". And FF7's major claim to fame will be performance enhancements and a widget to tell MOZILLA about webpage memory usage. So not only is Firefox 7 breaking the traditional model, it's reporting things to Mozilla that it won't even report to the user. Screw this, if I want phone-home enabled browsers, I'll go with the ones I already KNOW phone home, IE and Chrome.

    --
    Just because you're paranoid doesn't mean they aren't out to get you
    1. Re:performance enhancements? by Anonymous Coward · · Score: 0

      So not only is Firefox 7 breaking the traditional model, it's reporting things to Mozilla that it won't even report to the user.

      Citation needed.

      about:memory give detailed information to the user (especially in verbose mode), and sending memory information back to Mozilla is opt-in.

    2. Re:performance enhancements? by BZ · · Score: 1

      The telemetry information is opt-in. So nothing is sent unless you _explicitly_ tell Firefox to send it.

      If you want to see exactly what information is being gathered, https://addons.mozilla.org/en-US/firefox/addon/abouttelemetry/ will tell you.

    3. Re:performance enhancements? by waddgodd · · Score: 1

      The point here isn't WHAT information its gathering, it's that it won't tell me the same information when I ask.

      --
      Just because you're paranoid doesn't mean they aren't out to get you
    4. Re:performance enhancements? by BZ · · Score: 1

      I just pointed you to a way that you can ask it for that information and have it tell you. "What information" means "the exact data that is being sent in" (though it's presented in the form of labeled graphs, not JSON or whatever the submission format is).

  29. Firefox 100 in 2015 by wreakyhavoc · · Score: 1

    Something tells me they started feeling penis envy when FF was only 3.x.x and "theirs goes to 11". Add to that a fear that Avg Joe might think that FF technology is inferior due to the lower number.

    Will they be content to lay off this number madness when they reach parity with IE? Or will we be seeing version 24 in 2012, and Firefox 100 in 2015? At the current pace of releases, that may be a conservative number.

  30. Re:Whinedot - News For Complainers Stuff That Anno by sweatyboatman · · Score: 0

    Stifle criticism? Mozilla releases a beta version of their immensely popular web browser. I read the story on one of the most influential tech-blogs on the internet and instead of a discussion of the features of this new release there are a dozen uninformed posts about how changing the version number from 6 to 7 is a travesty!

    It breaks my pluginses, my precious!

    --
    It breaks my pluginses, my precious!
  31. There ain't no-one for to give you no pain by Anonymous Coward · · Score: 0

    "Those not current versions do not not get critical security updates except via the current version."
    Nice to see Asa's been working on the clarity of his communiques.

  32. Why should I care? by kbrannen · · Score: 5, Insightful

    Really, why should I care about FF any more? They're killing us and themselves with all of these major version releases. As many others have pointed out, it's painful when dealing with web development, plugin usage, or even just to know what version is "latest". And that doesn't count all the pain with the major bugs that just languish while the UI is endlessly tweaked for no good reason (exactly why was the status bar removed?).

    I'm sorry FF, but I'm sticking to the 3.6 series. As soon as that doesn't work anymore because of 1 OS upgrade too many, I'll stop using FF. If you can get things fixed and find sanity again before then, I'll stay. Otherwise, it's been a good 8 years we've had together.

    1. Re:Why should I care? by wreakyhavoc · · Score: 2

      Agreed. I need interface consistency. I want my muscle memory to work for me, not search around endlessly for some functionality that is now on the other side of the window or completely invisible now.

    2. Re:Why should I care? by Anonymous Coward · · Score: 0

      What are you going to do? Use Chrome? They look the same... and for good reason. This is where UI design for browsers is headed. However, if you want to re-enable your status bar, put the bookmarks toolbar back where it was, and make things look like 3.6.x. well then, there's nothing stopping you.

      No need to leave my friend.

    3. Re:Why should I care? by kangsterizer · · Score: 1

      And what will you use, Chrome? Because Chrome's no different.

    4. Re:Why should I care? by theweatherelectric · · Score: 3, Informative

      Firefox 4, Firefox 5, Firefox 6 and Firefox 7 beta have all been quite consistent in terms of the user interface. More releases hasn't equalled huge change in the UI in my experience.

    5. Re:Why should I care? by Anonymous Coward · · Score: 0

      I just switched from 7 beta back to 6 because Better Privacy didn't work yet.(although it hasn't been out long, and I'm sure other extensions won't work for a week or two.) I'm not a developer, so version numbers don't matter to me. But privacy does.

    6. Re:Why should I care? by surveyork · · Score: 1

      https://addons.mozilla.org/en-US/firefox/addon/add-on-compatibility-reporter/ This add-on "forces" add-on compatibility. A must have if you are trying out Fx betas, auroras and nightlies.

      --
      2019 is going to be the year of Linux on the desktop.
    7. Re:Why should I care? by Anonymous Coward · · Score: 0

      So you're complaining about what actually?
      What is "latest"? Latest is what's installed on your computer -- if you're only half the casual slashdotter i.e. starting up your computer and/or firefox at least once in 2 days and let it run it's less than 5 second update.

      If you're a developer, you can manage the not so great differences in FF5 and FF6. No major HTML5/css3 additions have been made.

      Quit whining

    8. Re:Why should I care? by xous · · Score: 0

      Really, why should I care about FF any more? They're killing us and themselves with all of these major version releases.
      >> Yes, because it's really hard to say yes to the update button and restart your browser.

      >>it's painful when dealing with web development
      Write proper standards compliant code and this ceases to be an issue.

      >> plugin usage
      Flame the shit out of your plugin devs. The new plug-in API has been static since FF4 and they intend to keep it compatible to resolve this issue. FF4 was released March 22, 2011 which means there is absolutely no excuse for plugins to not be compatible with FF4-7.

      >> or even just to know what version is "latest".
      Help > About.

      >> And that doesn't count all the pain with the major bugs that just languish while the UI is endlessly tweaked for no good reason (exactly why was the status bar removed?)
      It wasn't removed. It was upgraded and renamed. View > Toolbars -> Add-on Bar.
      It's not enabled by default to give more screen real estate. I don't agree with it but it takes half a fucking second to adjust.

      As always it's just a fucking number. Who cares if they increase by +1 instead of +0.1 or +1,000,000.

    9. Re:Why should I care? by multipartmixed · · Score: 2

      The status bar wasn't just renamed, it was seriously improved now that it's a general-purpose bar, rather than *just* a status bar.

      I put my location bar in it, so that I look at the bottom of the screen when typing in a URL, but at the top of the screen when looking for a tab. Keeping my head moving like that helps my neck.

      So, to summarize: old - cannot be customized. new - can be customized, off by default.

      I agree with you, not such a huge pain.

      --

      Do daemons dream of electric sleep()?
    10. Re:Why should I care? by Anonymous Coward · · Score: 0

      Same, also still on 3.6. I dont know why but I lost trust in Mozilla with this mad cycle they entered. The weirdest thing is is that I keep all of my software up to date to the latest version if possible...

  33. Re:Whinedot - News For Complainers Stuff That Anno by Anonymous Coward · · Score: 1

    Stifle criticism?

    Did you not read the bugzilla thread where Asa Dotzler was getting butthurt and trying to stifle debate because people *gasp* dared to question his supposed "bug"?

    Once again, if you don't want anyone criticizing something. DON'T FUCKING RELEASE IT TO THE PUBLIC. Mozilla seems to want to turn Firefox into a circle jerk fest. That's fine, just keep it to yourselves and circle jerk away.

  34. Huh? by Anonymous Coward · · Score: 0

    There was a Firefox 6? I just upgraded to 4 a month ago and then to 5 last week. Both times, it was the latest available. :P

  35. Re:Really? What's the point of this version number by JMJimmy · · Score: 3, Interesting

    What do you use instead? That's been my big problem - the plugin libraries of other browsers are no where near as extensive and a lot of the functionality I use daily just isn't there.

    Plugins used daily:

    - Snap Links Plus ---- a few upgrades and this should replace traditional highlighting in a browser
    - QuickDrag ---- removes the need to do ctrl+click to open in a new tab
    - Adblock Plus ---- simply hiding ads isn't enough for ABP, it must stop them from downloading to preserve the precious 20gb of data transfer/month I have
    - Element Hiding Helper ---- for those few pesky ads you can't block from downloading
    - Modify Headers ---- this one is gold
    - FireFTP
    - Canadian English Dictionary
    - IE Tab Plus ---- for those pesky active x controls (not used daily but useful)
    - Morning Coffee ---- how else would I open all my favourite sites at once? certainly not with the "dialpad" or whatever that monstrosity is called
    - Chatzilla
    - about a dozen different web development tools from Firebug to Live HTTP headers to MeasureIt... just too many to mension

    There's just no option that does all that... at best I might be able to do it across 4-5 different programs if I dropped some of them. Slowly though they are no longer supporting 3.6 and I won't upgrade due to the numerous issues from their release model to their UI and so on... eventually I'll have switch to another browser because neither 3.6 nor 7+ will be worth using.

    It was good while it lasted.

  36. Versioning. by richie2000 · · Score: 2

    I think some hacker redefined Mozilla's $version as an INT.

    --
    Money for nothing, pix for free
    1. Re:Versioning. by Anonymous Coward · · Score: 0

      With an auto_increment trigger before update of each row

    2. Re:Versioning. by Anonymous Coward · · Score: 0

      John Titor emailed me some Firefox change logs from next month.

      Changelog for Firefox 15:
      September 2, 2011
        * Fixed typo in advanced options panel.

      Changelog for Firefox 16:
      September 3, 2011
        * Updated version to Firefox 15 since we forgot to change the version number in the last update.

      Changelog for Firefox 17
      September 4, 2011
        * Updated version to Firefox 16.

      Changelog for Firefox 18
      September 5, 2011
        * Updated version to Firefox 17.

      Changelog for Firefox 19
      September 6, 2011
        * Updated version to Firefox 18.

      Changelog for Firefox 20
      September 7, 2011
        * Updated version to Firefox 19.

  37. Re:Really? What's the point of this version number by arth1 · · Score: 4, Insightful

    You could use the super-secret Mozilla Add-on SDK

    QUOTE: help ensure your add-on continues to work as new versions of Firefox are released.

    Nobody seems to be mentioning this solution. Not even Mozilla.

    At least in part because having Firefox auto-update the xpi to mark it compatible for a new version breaks when modules are signed.
    So for those, the developer has to release a new package. And if your release cycle is 6 months (fairly common), and Firefox' release cycle is 6 weeks, there is going to be Problems.
    Both users and developers aren't going to put up with it, and will leave. Which is exactly what we see happening now - it wasn't rocket science to predict this outcome.

  38. Re:Radical idea: Fix the plugin api! by uniquename72 · · Score: 1

    Seriously. I NEED Firefox because it has some extensions that Chrome doesn't have, but at this point FF has driven me away for 80% of my browser time.

    Thanks to constantly breaking extensions, I've stopped automatic updates, and now plan on checking back with FF every 5th release or so to see if I should bother updating.

  39. Improve Perfomance by disabling add-ons by nurbles · · Score: 1

    Now that Mozilla is releasing new versions of Firefox every time the add-on writers get caught up, it is no surprise they're claiming performance improvements!

    1. Re:Improve Perfomance by disabling add-ons by Culture20 · · Score: 1

      Indeed. I just updated to FF6 on some weblab computers and addons like the latest Java, Adobe Reader, etc all broke. WTF Mozilla?

  40. Re:Really? What's the point of this version number by arth1 · · Score: 1

    What do you use instead? That's been my big problem - the plugin libraries of other browsers are no where near as extensive and a lot of the functionality I use daily just isn't there.

    That is indeed the problem. But there comes a point where one has to cut one's losses and move on, despite being as tied in to Firefox as the average company is to Office.

    In my case, I find myself using Midori (Webkit based) more and more, because it's fast, lean and even more standards-compatible than Firefox. Sure, it means dropping most extensions, although it does run plugins (by setting MOZ_PLUGIN_PATH and ). And they don't bump versions every other week.

    In Windows, IE is coming back, and even though I don't like MS much, it is now has to be considered a viable alternative to Firefox.
    Yeah, Asa Dotzler managed what no-one else has done - make me switch to a Microsoft product out of sheer desperation.

  41. Re:Really? What's the point of this version number by Anonymous Coward · · Score: 0

    Yeah, switch to IE6, it has the stability you want.

  42. Re:Really? What's the point of this version number by JMJimmy · · Score: 1

    IE is a switch I'd never make. UI issues aside it's clunky and slow, even with the upgrades. The biggest drawback for me in IE is a seemingly minor one... that you can't access the address bar when first opening the program until the onload event is fired. I get so frustrated at this when using others computers - granted the simple fix is to simply load about:blank. It makes large session saving impractical though.

    I would so fork 3.6 if I had the technical know how.

  43. Fuck Firefox. by Anonymous Coward · · Score: 0

    I was a Mozilla browser user before Firefox existed. When Firefox first came out (it wasn't called Firefox then, first it was "Phoenix", then it became "Firebird" later), I eventually transitioned over to it as my primary browser. Tabs weren't common in browsers back then, and Phoenix was much lighter than full-on Mozilla. It ran on Windows and Linux. All around it was a big win.

    The reason I liked it so much was that it looked the same on all three of the platforms that I used: Mac & Linux for personal use, and Windows at work. My brain only needed to remember one set of icons & icon locations. All was good.

    Recently (around FF 4, I think), they started switching around the UI. The UI looked more or less the same the entire time I've been using it, over 8 fucking years, but now, all of a sudden, I upgrade it and everything is different. Now every time I install Firefox somewhere, instead of just installing adblock, I have fiddle with it until it looks the same as it used to. It's not the change that bothers me. It's that they didn't improve its usability at all. As far as I can tell, the cosmetic changes to Firefox were just to make it look more like Chrome.

    And now this version number debacle... I don't want to see a box asking me to upgrade my browser every fucking week. I don't want to have to press "Later". I don't want to know about it. I don't want to watch it grind away for a few minutes "installing updates" when I close the last window and re-launch the app.

    So fuck you, Mozilla. I switched to Chrome. It's mature enough, adblock works great for it, and the sync feature works far better than the FF sync ever did. Doesn't harass me about updating. And it looks the same as it did the last time I saw it.

    1. Re:Fuck Firefox. by Ash-Fox · · Score: 1

      Firefox changes UI and version releasing to Chrome's methodology.

      So fuck you, Mozilla. I switched to Chrome.

      LOL

      --
      Change is certain; progress is not obligatory.
  44. Extensions by Jazari · · Score: 1

    So am I the only one still using Firefox 3.6.x ? I have a lot of extensions that I like, and I know they'll break if I update. But at the rate Firefox is updating, the extension writers just can't seem to keep up.
    Without extensions, I might as well just switch to Chrome.

    1. Re:Extensions by Culture20 · · Score: 1

      Thankfully I'm using a distro that won't update from 3.6 too soon. But that means my support calls with my parents for FF6 and TB5 are more difficult.

    2. Re:Extensions by vlueboy · · Score: 1

      I remember the days of supporting students with Win95, 98, ME, 2000 --all "different," yet all "alike". You have rightly outlined a perfect excuse for forcing friends to software we only know less intimately, but that guarantee to update less so that we can keep up with feature placement and support.

      Safari for Windows FINALLY implemented fullscreen support in 5.1 a month ago. In imitation of American credit rating bureaus so popular these days, Vlueboy has evaluated this improvement and is raising Safari's usability rating to "widescreen A+"

      I'm writing this from 3.6 on Windows; though I have to admit minefield is on the other computer at version 8, which won't be out till early 2012.

    3. Re:Extensions by Anonymous Coward · · Score: 0

      "Minefield 8"? You mean "Aurora 8". Minefield is no more. The times are a'changing.

  45. A Numbers Game by Anonymous Coward · · Score: 0

    It's all about getting up to and beyond Internet Explorer's version number so they can appear to be on par with or surpassing IE as perceived by the common end user. This is very much like why Microsoft decided to go with XBOX 360 instead of XBOX 2 when the PS3 was numbered.

  46. Firefox 4.3 Beta Released by Anonymous Coward · · Score: 0

    Hope that number clears it up for you if you're still reeling from seeing 5.0 so soon.

  47. Poll suggestion by Anonymous Coward · · Score: 0

    How about a poll asking firefox users which version of FF they are still running? I bet the majority is still running 3.6 for addon compatibility.

  48. Re:Really? What's the point of this version number by perryizgr8 · · Score: 1

    snap links plus- sounds mildly useful
    quickdrag- wtf?? ever heard of middle click??
    abp- chrome has it now.
    element hiding- abp does this in chrome
    modify headers- i don't need this, and i suppose you also don't *really* need it.
    fireftp- useful
    canadian english- lol wut?
    ietab- chrome does this 100x better
    morning coffee- i dunno anything about this one, but if you just wanna open some websites at once, you can create a bookmark folder or something.
    chatzilla- people still use irc in the age of fb and gmail chat?
    dev tools- agree

    so i think you would agree that now is the time to switch.

    --
    Wealth is the gift that keeps on giving.
  49. Re:Really? What's the point of this version number by perryizgr8 · · Score: 1

    ie9 is actually a pretty sweet alternative to ff now. its very fast, clean ui, and does not freeze up like ff does. also, there's no performance hit of opening a lot of tabs. also it has very nice gpu acceleration and uses much less battery. but i still stick to chrome just because it is as fast as ie9, and also has loads of extensions.

    --
    Wealth is the gift that keeps on giving.
  50. Re:make the update notifications more annoying ple by Anonymous Coward · · Score: 0

    Oh! And I hope they start forcing the icon onto the desktop with each update, Adobe style; that would rock.

    OH GOD PLEASE, NO...

  51. Ditching the High Maintenance Broad by jazman_777 · · Score: 1

    I'm wiping Firefox entirely off computers at home, just can't be bothered to deal with a high-maintenance broad, er, browser.

    --
    Slashdot: Failed Car Analogies. Amateur Lawyering. Anecdote Battles.
  52. Still can't print by Anonymous Coward · · Score: 0

    4 "major" revisions later, and it still can't print multi-page fieldsets (spoiler alert: truncates your data and prints borders as though that data was never there), a show-stopping bug introduced over 3 years ago. Numerous bug reports removed as "duplicates" yet the bug still isn't addressed. It is a sad day (or 3 years) that as a dev I feel I can rely on IE9 better than Firefox, and bugs I find and report for IE actually get fixed. (Not to mention render times and responsiveness are just fine in IE these days)

    Mozilla's official response: "No. This is going to lead to splitting of fieldset frames, which the fieldset code is not set up to handle."

    1. Re:Still can't print by Anonymous Coward · · Score: 0

      <style type="text/css">
      @media print { fieldset { display: none } }
      @media screen { .printable { display: none } }
      </style>
      <fieldset>
      <!-- fieldset for filling out in-browser -->
      </fieldset>
      <span class="printable">
      <!-- printer-friendly version of form -->
      </span>

      Wow, that was really hard...

  53. Re:Really? What's the point of this version number by JMJimmy · · Score: 1

    modify headers- i don't need this, and i suppose you also don't *really* need it.

    Web development reasons aside, getting around certain regional restrictions makes this one invaluable. Anything on MTV Services, BBC, etc - all easily tricked with the X-Forwarded-For header. Sadly not Hulu.

    quickdrag- wtf?? ever heard of middle click??

    Ever heard of not having a mouse wheel? Like on a laptop! I also find it much faster than middle click personally.

    abp- chrome has it now.

    Last I researched it, which was admittedly a while ago, ABP in Chrome just hides elements but still downloads them to the system. For me it's less about not seeing the ads and more the speed increase and data savings not having to download all that crap. That said, I still like getting rid of the ads so ABP Chrome does hold some value.

    morning coffee- i dunno anything about this one, but if you just wanna open some websites at once, you can create a bookmark folder or something.

    Yeah, this one just has nice day of the week features so work stuff is opened Monday-Friday and Everyday my usual sites are opened - all in one click - or - as my home page. Very much a convenience thing which I could give up if need be.

  54. Re:Really? What's the point of this version number by JMJimmy · · Score: 1

    PS: Not on Facebook (was, left after the ToS changes years back... haven't missed it a bit) and gmail chat gets blocked by ABP so it doesn't load every time I check gmail. Skype is my IM of choice for personal stuff (so looking forward to Xbox integration) and Chatzilla for professional/hobby chat.

  55. Re:Really? What's the point of this version number by perryizgr8 · · Score: 1

    my laptop can be configure to act out a middle click if i press both buttons, or if i do a double finger tap. i thought all laptops could do this now? how is a tap on the touchpad slower than ctrl+tap?
    i'm not sure about this but i think abp in chrome actually does block ads, not just hide them.

    --
    Wealth is the gift that keeps on giving.
  56. The best new Firefox 6 feature for web developers by Anonymous Coward · · Score: 0

    ...removal of the useless "View Source" menu item.

  57. The version is marketing by Oxford_Comma_Lover · · Score: 2

    Version numbers these days are more about marketing than informational content. Based on no knowledge of the politics of the decision or any formal statements issued to the contrary, it really seems like someone signed off on a corporate plan to bring Firefox version numbers up to match or exceed IE version numbers.

    At least, that would be the best explanation for it that comes to mind. It's really weird for tech people to see, but it may help convey the relative maturity of the browser to new laypeople.

    --
    -- IANAL, this isn't legal advice, and definitely isn't legal advice for you. Also, Squee!
  58. DGAF by Anonymous Coward · · Score: 0

    'Nuff said.

  59. Re:Really? What's the point of this version number by JMJimmy · · Score: 1

    Re: ABP Chrome, I did a little digging and in fact all AdBlockers on Chrome hide elements and do not truly block them due to a limitation (or restriction?) in Chrome itself. It also does not block ads in videos with the exception of YouTube.

    For me I disabled taping on the touch pad - I would trigger a tap every time I'd go to two finger scroll on the touchpad or start a mouse movement. Gesture based interfaces are great if you can get used to them/have good fine motor control, if you don't they're all but useless for more than a couple actions (I leave 2 finger scroll enabled and that's it). I also found leaving it enabled that my right thumb would trigger clicks while I was typing due to the position of the mouse relative to the F and J keys on this laptop. It's centred below the N key instead of below the B so the top right corner is directly under my thumb as it rests on the space bar.

    I did try the both button workaround, more often than not I'd click one button before the other which resulted in either opening the page in that tab (instead of a new one) or clicking the bottom item in the context menu. For whatever reason Left-Click+Hold+Drag+Release works really quickly/easily/accurately for me. Even faster if I have an actual mouse plugged in.

  60. Mozilla should do like the linux kernel developers by nej_simon · · Score: 1

    Release often with new features, but once in a while realase a long term version that's maintained for at least a year or two for those who require stability.

  61. Re:Really? What's the point of this version number by isorox · · Score: 1

    - QuickDrag ---- removes the need to do ctrl+click to open in a new tab

    That's what the middle button does

  62. Where did it go? by Anonymous Coward · · Score: 0

    I don't care about the "lack of support" for previous versions of FF, but they could at least put up previous versions in an easily accessible place so people could revert back to old versions if they want to. It took a good 15-20 minutes of browsing before I found the ftp server that allows you to download previous versions. The only archive they have on their website is for various languages of 3.6.2. There is absolutely no record whatsoever of 4, 5, or 6!

  63. Re:Really? What's the point of this version number by Shikaku · · Score: 1

    Why is this modded up?

    You can use all of these. Actually I AM USING ALL OF THESE IN 6.0.
    http://portableapps.com/apps/internet/firefox_portable
    https://addons.mozilla.org/en-US/firefox/addon/febe/

    1. backup your profile. If you are on windows or you can't command line on linux, use FEBE (yes there's a 3.6 version (scroll down and look in version information), yes it works cross versions), or if linux, cp -r ~/.mozilla ~/.mozillabackup to backup your profile.
    2. if windows, use portable firefox. otherwise on linux download the latest executable from the site. you must backup your profile somehow in step one before you do this to allow you to revert and use your settings if you decide to keep your settings. if you are paranoid that some obscure setting wont save use a portable 3.6 and try to clone it.
    3. test the new version. if you used portable firefox, you can use FEBE to transfer settings to a real install (portable versions can lag behind drastically). revert if you are pedantic, impatient to configure and install new ui extensions to fix things (like statusbar 4eva, tab mix plus, etc.), or have serious problems.

    Literally, don't go apeshit about it. You can do something about it, without addons breaking. New in 6.0 is heuristics for AMO (addons.mozilla.com) plugins to be auto version bumped for beyond versions. You're just gonna whine about it and not take the time to research, nor voice your concern to mozilla, nor know all the facts. By the by, i agree, mozilla should add for enterprise and people who want stability: Stable version and rapid release version of firefox.

  64. XUL by anarkhos · · Score: 1

    Performance enhancement? Does that mean they finally got rid of XUL?

    --
    >80 column hard wrapped e-mail is not a sign of intelligent
    >life
  65. Tabs no longer on top by rbpOne · · Score: 0

    I just installed the Aurora channel firefox alpha 8. In FF8, tabs are not longer on top as default.

    And ive just gotten used to them...

  66. Re:Really? What's the point of this version number by JMJimmy · · Score: 1

    a) The UI sucks hard in 4+
    b) Just because it auto-version bumps doesn't mean it won't break the addon. Prior to this the addon developers had time to deal with code changes in Firefox before a major version release. Now with new versions coming out frequently they'll be scrambling to test/update for one version and the next will already be out. That may be fine for some of the major plugins but the small developers won't bother to keep up with that pace.
    c) Why the f**k should a user have to go through all that trouble for an upgrade let alone every 6-8 weeks or so?

  67. I'm still on 3.6.18... by Anonymous Coward · · Score: 0

    ... and it's working fine. I've downloaded 3.6.19 and I'll probably hold onto that installer just in case there's not another 3.6 dot release. I don't plan to upgrade any higher until the dust settles.

    For extensions, I use the following, and I feel quite secure:

    BetterPrivacy
    Certificate Patrol
    Cookie Monster
    Flashblock
    HTTPS-Everywhere
    NoScript

  68. Too little, too late. by DiSKiLLeR · · Score: 1

    Firefox 4, 5, and 6 were piles of overbloated resource hogging pieces of SHIT.

    Firefox 7? Too little too late, my friend.

    I've been using Mozilla from before the firefox days, hell I even used firefox before it was called firefox (remember phoenix anyone?), but firefox truly has gone the bloated route now.

    Both IE9 and Chrome are now FAR better browsers than Firefox 4/5/6.

    I've personally switched to Chrome everywhere, and looking at getting the entire office at work switched from Firefox to Chrome as well (the rapid release cycle of Firefox is nuts, its more rapid than even Chrome and the browser only gets worse with each new release anyway.)

    --
    You can tell how powerful someone is by the magnitude of the crime they can commit and be able to get away with.
  69. Re:The best new Firefox 6 feature for web develope by Oligonicella · · Score: 1

    You mean Ctrl-U or Firefox/Web Developer/View Page Source?

  70. No URL schemes?! by Rizimar · · Score: 1

    They felt the need to get rid of the protocols/schemes in the Address (er, I mean "Awesome") Bar. Apparently, it's because the developers think that it will put more focus on the actual page within a website by allowing more room for it to be displayed. But I'd argue that the server is pretty important, especially for us web developer types, and how we connect to a server is a vital piece of knowledge. I mean, the scheme is necessary for a valid URL.

    I don't know about anyone else's displays, but my browsers all have sufficient space to show the full URL most of the time. If not, it's not a hassle for me to click and see the end of it if I really need to. Usually, I know where I am on the web based on how I got to that page as well as the page itself. I don't think we need these silly URL omissions. What's next, hiding URL parameters? Removing the favicon?

    For anyone else who feels my frustration, you can bring back the schemes pretty easily:

    1. - Type about:config in the Address Bar
    2. - Find browser.urlbar.trimURLs
    3. - Right click it and select Toggle

    Bam. Your suffering has been relieved.

  71. The assumption of what is likely is your own by Anonymous Coward · · Score: 0

    Could you please point out in these blog posts where the "current practice" is what you described it as?

  72. Re:Really? What's the point of this version number by Shikaku · · Score: 1

    a) I still have the same UI. There's a right click setting if you do a fresh install to revert to the old UI. If you upgraded you get the old UI. If you are pedantic there are more UI mods to make it more "normal." I see you never found the menu.
    b) Read the release notes and you'll see why they don't break. You're literally too lazy to do anything like a typical American. I would also read the definition of heuristic, since it is extremely important. Also I would like to add that changes have been moderate but not major after 4.0 so far and only added new HTML5 technologies and memory fixes. 6.0 took care of your concern about add-ons breaking as the main feature.
    c) The instructions only apply once. You can backup your settings using FEBE regularly (which by the way can be set to be automatic and with online syncing services like Dropbox or the built in Box.net syncing make it redundant and saved for anywhere) and if something breaks, you can just revert and restore. Again, too lazy to complain to mozilla and not slashdot, where they will gloss over it as angry ranting.

    I'm literally telling you how to fix it yet you just trash it. Nevermind that with something as customizable as Firefox, things can (and have) change drastically and Mozilla will be stuck in a hard place if they must change the way Firefox works like they had to starting with 4.0.

    You're welcome, I guess.

  73. Why won't Mozilla listen? by plastick · · Score: 1

    I use Firefox for the extensions (as do most others). If they break the extensions, then there's no need for the vast majority to use Firefox.

    Why they are refusing to listen to the users and keep such an biased attitude is beyond me. You know Microsoft and Google are grinning ear to ear.

    Lastly, why would you remove features/functionality (for example the status bar), and then give no way to turn them back on?? It's going backwards and actually losing functionality! That's "better"??

  74. Promises by Anonymous Coward · · Score: 0

    They have been promising a "normal" memory consuption and responsivenes since the 2.0/3.0 times. We are almost in version 9.0 already and havent seen any of it. So no thanks, i'll stick with Chromium. Has all the plugins I need and is infinetly more faster in every aspect than Firefox.

  75. Re:Really? What's the point of this version number by JMJimmy · · Score: 1

    a) I have another computer with Firefox 7 on it and while you can get the file menu back the UI does not revert to the old style. I should not have to install a crapload of addons to fix UI problems that did not exist in previous versions and were entirely of Mozilla's making.

    b) I'm not American but I see you are an assumptive pre-judging ass. I understand the definition of heuristic just fine. Take something as simple as the "Undo Close Tab" extension - technically speaking it will install and "work" in 7 just fine. Unfortunately you can no longer place it anywhere on the UI like you previously could, FF only allows it to be install on the tab bar where it's awkward and gets in the way. It also doesn't function as expected because Mozilla made several adjustments to how tabs work through 4-7 which broke it. The developer isn't hugely active and can't keep adjusting his script with every new change to tabs.

    c) Great, yet another piece of software that has to run in the background on my system tying up resources for a problem that need not exist. I've complained to mozilla repeatedly in several different forms but they could care less about what users want they just do what they want. Don't believe me? I can show you years old bugs where the only dissenting voice is Mozilla and even then some of the Moz devs are onboard but still can't implement what users want.

  76. Firefox has always been second best by Jadeus · · Score: 1

    When Firefox came out, and Mozilla became deprecated, that ended my (unusually supported-by-management) attempt to replace Outlook/IE on our desktops. Firefox was slow and crappy, but Mozilla (the browser) was fast and good, and it's suite had the tools we needed. This was my impression even having run all the milestone builds, which had a pain level about the same as passing stones -- ie, about 1/10th that of running Netscape 4. Admittedly NS4 sucked so bad that in comparison anything was better... hell, I even converted a few to IE just to get away from that POS.

    The alternatives were Lynx, wget and telnet * 80, so Firefox it was for desktop-oriented HTTP requests.

    The day Chrome was released was the day that Firefox stopped getting used on my desktop. At home it's been a great time. At work I get wrist slapped every 9-12 months by IT Security ("off the top of my head, uh, security reasons" no sh!t) but it's been so worth it to spend my days Fsckingslowfox-free.

    FF has been garbage since day 1. Slow, crashy, unresponsive. Their mentality towards the people who use it is flabbergasting and demonstrates a total lack of understanding/experience in the field. Truly offensive.

    The fact that people are up in arms _only over plugins_ should be enough indication that the core product is worth very little. Nobody gives a rats ass about Firefox, they care about plugins developed by individuals and companies who, IMHO, seem to be far smarter than those behind the platform they build on.

    Good riddance.

    --
    --- Bigger bits, softer blocks, tighter ASCII.
  77. Tabs in window titlebar by cerberusss · · Score: 1

    On Linux, they aren't yet putting the tabs in the window titlebar. The screenshots show the usual Windows version, which looks awesome compared to what I see when I run it on Debian.

    --
    8 of 13 people found this answer helpful. Did you?
  78. Re:Radical idea: Fix the plugin api! by Anonymous Coward · · Score: 0

    first it were plugins, then extensions, now its called addons. lets see how mozilla calls it tomorrow.

  79. Re:Radical idea: Fix the plugin api! by Anonymous Coward · · Score: 0

    No, it weren't neither.

    Plugins are plugins and always have been. Some plugins: Flash, Java, Adobe Reader. Plugins run only when a page calls for them.
    Extensions are extensions and always have been. Some extensions: ABP, FEBE, NoScript. Extensions can run whenever they want to.
    Add-ons is an inclusive term which refers to plugins and extensions and themes.