Slashdot Mirror


Mozilla Firefox 2.0 Alpha Peeking Out (Or Not)

anadgouda writes "Mozilla Firefox 2.0 alpha is released. The links for download were not available directly on Mozilla.com website. Being Alpha, all features might not work and most of the plugins might not be compatible." Reading thru the comments, it appears there's some disparity as to whether or not this is actually just a naming scheme that they use; but let me reiterate that there has been no official announcement from Mozilla, so take with a giant grain of salt. Some good screenshots at OSdir.

216 comments

  1. I'd consider alpha if I knew new features. by yagu · · Score: 4, Informative

    Okay, seemingly little to no information about what comprises the new Firefox. For those who also might be curious, I have found these features described in a Firefox 2 Roadmap, but don't know if and how many of these made it to the new release.

    Anyone else have any links to release notes?, what's new in FF 2?

    1. Re:I'd consider alpha if I knew new features. by phillips321 · · Score: 2, Informative

      Don't rush to upgrade guys, remember, there will be alot of problems with your extensions until they are upgraded to be compatible with the new release.

    2. Re:I'd consider alpha if I knew new features. by dolphinling · · Score: 5, Informative

      No it is NOT released.

      See Asa Dotzler's blog post

      --
      There are 11 types of people in the world: those who can count in binary, and those who can't.
    3. Re:I'd consider alpha if I knew new features. by poeidon1 · · Score: 1

      well then! wait for the offical release.

      --
      They called me mad, and I called them mad, and damn them, they outvoted me. -Nathaniel Lee
    4. Re:I'd consider alpha if I knew new features. by bunratty · · Score: 4, Insightful

      Unless you're fairly deeply involved in QA (i.e. you have a Bugzilla account and plan to report bugs you find), just skip alpha versions and stick with a stable release. Wait until the beta or a release candidate is out much later this year.

      --
      What a fool believes, he sees, no wise man has the power to reason away.
    5. Re:I'd consider alpha if I knew new features. by MyShinyMetalAss · · Score: 0, Offtopic

      There are 11 types of people in the world: those who can count in binary, and those who can't.

      And then there is you.

      --
      This is not an automated signature. I type this in to the bottom of every message.
    6. Re:I'd consider alpha if I knew new features. by Anonymous Coward · · Score: 0
      Yes, it IS released.

      /posting using FF 2.0 alpha. pwn3dz!

    7. Re:I'd consider alpha if I knew new features. by Bozzio · · Score: 2, Funny

      That's the joke.

      from audience: You suck, McBain!

      --
      I just pooped your party.
    8. Re:I'd consider alpha if I knew new features. by paraax · · Score: 1

      Well, he's just counting in unary. (1 = 1, 11 = 2, 111 = 3, etc.)

    9. Re:I'd consider alpha if I knew new features. by moro_666 · · Score: 2, Insightful

      I think it's extremenly annoying how lightly they take the braking of backward compatibility. Please spend 1 month more on proper planning and datastructure design and get a standard out that will let the extension work for at least 2 years.

        I just finished upgrading the last extensions to 1.5, and already you're going to break it again :S

        If the new datastructure design doesn't really flex along the old model, make a freaking sandbox that runs the old extensions in an emulated mode which is on-the-run translated to the new calls.

        Sure new features are insteresting and new possibilites tempting, but it's hard to keep track all the time. If backward compatibility can't be done, do the sandboxing and emulation. I don't care how slow it gets, i want it to work.

      --

      I'd tell you the chances of this story being a dupe, but you wouldn't like it.
    10. Re:I'd consider alpha if I knew new features. by MindStalker · · Score: 1

      I just figured he was miscounting in binary and thats the joke. Assuming he counts in unary is like assuming Douglas Adams makes jokes in base 13.

    11. Re:I'd consider alpha if I knew new features. by jp10558 · · Score: 1

      And this is one of the biggest things that negates extensions value for many people considering FireFox.

      --
      Opera, Proxomitron-Grypen,GPG 0x0A1C6EE3
    12. Re:I'd consider alpha if I knew new features. by Anonymous Coward · · Score: 0

      So this is just news for nerds and not regular users. It probably should never have been posted here at Slashdot then.

    13. Re:I'd consider alpha if I knew new features. by Anonymous Coward · · Score: 0

      This is caused by extension authors as well. The current documentation tells them to use "1.5.0.*" for maxVersion so that their extensions will continue to operate for the bugfix and security updates to 1.5(currently 1.5.0.1; 1.5.0.2 forthcoming). Looking at the 16 extensions I have currently installed(not all of them are enabled), exactly 1 has maxVersion="1.5.0.*".

    14. Re:I'd consider alpha if I knew new features. by catprog · · Score: 1

      Why?

      part of Slashdot's motto is "news for nerds"

      --
      My Transformation Website
      Kindle Books http://www.catprog.org/rev
      Interactive CYOA http://www.catprog.org/st
    15. Re:I'd consider alpha if I knew new features. by hairyfeet · · Score: 1
      I'm running Bon Echo right now (The code name for FF 2.0a1) and the biggest new feature is the places button.With the places button you can bring up a search box that checks your bookmarks,history,RSS feeds,etc for any keyword.

      While I like FF as a guest browser and welcome the new places feature,I'm going to have to stick with Seamonkey.The combination of roaming profiles+Multizilla makes it too damn handy to let go of.That said I always keep a copy of FF on all my machines for guests as FF is so much more "new user friendly" than my Seamonkey.(And it gives me a great excuse to keep people out of my browser,LOL)

      --
      ACs don't waste your time replying, your posts are never seen by me.
    16. Re:I'd consider alpha if I knew new features. by Anonymous Coward · · Score: 0

      And you oblviously belong here.

    17. Re:I'd consider alpha if I knew new features. by richlv · · Score: 1

      argh. there should be one 'emergency modpoint' for cases like this :)

      --
      Rich
  2. NOT released. by Myen · · Score: 4, Informative

    Mozilla Firefox 2.0 alpha NOT released.

    The nightlies are now branded 2.0 alpha because... well, for some odd reason they like to brand their CVS builds before things get released, to make sure the act of rebranding breaks nothing. IIRC that actually hit them way back and they got scared.

    Firefox 2.0 will be considered released when you see it on www.mozilla.org / www.mozilla.com / irc.mozilla.org

    1. Re:NOT released. by dolphinling · · Score: 5, Informative

      What's sad is the "article" links to tinderbox builds, not even the official nightly development builds!

      People really should not submit articles if they have no clue what they're talking about.

      --
      There are 11 types of people in the world: those who can count in binary, and those who can't.
    2. Re:NOT released. by osgeek · · Score: 4, Insightful

      People are going to be idiots... you would hope to see better from the editors, though.

    3. Re:NOT released. by Anonymous Coward · · Score: 0

      Well, the editors are people too ;-)

    4. Re:NOT released. by Tim+C · · Score: 1

      People really should not submit articles if they have no clue what they're talking about.

      People really should not approve articles if they have no clue what they're talking about.

  3. It's NOT released yet! by Anonymous Coward · · Score: 5, Informative

    Quote from Asa Dotler's blog:
     
      When we make a new release, we'll say so. Please don't report new releases because someone checks in a change to the user agent or similar. If we're actaully doing a release, we'll announce it. Thanks.

  4. Missing like Bueller by fatduck · · Score: 1

    No undo close tab? Say it isn't so!

    --
    Making you think you're crazy is a billion dollar industry.
    1. Re:Missing like Bueller by shreevatsa · · Score: 4, Informative

      Tab Mix Plus is an extension that has the "Undo Close Tab" feature, as well as many other useful ones. (The extension's page on the mozilla site is here.)
      If you want only Undo Close Tab, that feature is also available in an extension called (what else?) undoclosetab.

    2. Re:Missing like Bueller by luder · · Score: 1

      You can also use SessionSaver. To restore a tab, go to Tools and select SnapBack Tab.

    3. Re:Missing like Bueller by Misagon · · Score: 1

      I don't use tabs. I open lots of multiple windows that I "shade" in WindowMaker, so I have to wish for an "undo close window" option.

      Window shading has the feature that there is always enough space for the whole title. I can also group pages/windows together.

      --
      "We mustn't be caught by surprise by our own advancing technology" -- Aldous Huxley
  5. Features and more from the status meeting by Lord+Satri · · Score: 4, Informative

    I was looking for the same thing as you, documentation about the features. You provided an interesting link, here's another one from the latest status meeting which includes the features, but a lot more :-)

    1. Re:Features and more from the status meeting by Random+BedHead+Ed · · Score: 1

      Thanks for that. Here's a feature from that link I really like: Undo Close Tab. I can't think of how many times I've accidentally closed a tab and wished I could get it back.

    2. Re:Features and more from the status meeting by Medieval_Gnome · · Score: 1

      I believe this might be what you're looking for. It also recovers your session in the case of a crash (either browser or OS)

      --

      :wq

    3. Re:Features and more from the status meeting by Scaba · · Score: 1

      I find the session saver in Tab Mix Plus to be more robust than the session saver in Session Saver. YMMV.

  6. Linux is a Minix clone by BadAnalogyGuy · · Score: 2, Insightful

    Where's the link?

    Where would we be today if Linus came along and said, "Well guys, I'm working on a Minix clone and it's going to be totally k-rad, and I'll keep the development open to anyone who wants to help out, but you can't download it anywhere. Sry, kthxbye!" ?

    Not that the Firefox team is all that willing to let anyone just start developing the core stuff, but note the nick and try not to concentrate on that.

    1. Re:Linux is a Minix clone by dolphinling · · Score: 1

      There is no link because, as plenty of people have pointed out, it's NOT released yet.

      However, if you do want to develop it, the entire sources (trunk and many branches) are available through CVS, see the DevMo page on the subject.

      --
      There are 11 types of people in the world: those who can count in binary, and those who can't.
    2. Re:Linux is a Minix clone by a_nonamiss · · Score: 0, Offtopic
      There are 11 types of people in the world: those who can count in binary, and those who can't.

      And what is the third type? :p

      OK, OK... I get the joke. :)
      --
      -Arthur
      Cave ne ante ullas catapultas ambules
    3. Re:Linux is a Minix clone by Anonymous Coward · · Score: 0

      This would be a good analogy if Linux were a Minix clone. Minix was the platform he developed on. He wasn't cloning it. This has already been documented several times on the Net. http://www.groklaw.net/article.php?story=200405200 21144762/

    4. Re:Linux is a Minix clone by luserSPAZ · · Score: 1

      You are welcome to download the source code and start fixing bugs. If you'd like to hack on core features, go ahead. Of course your code will need to pass review to make it into CVS, but that's pretty standard. Also, there are builds available *every single day* constituting the current CVS code. If that's not open and available, I don't know what is.

  7. Is this the present or the past? by illtron · · Score: 1
    "Mozilla Firefox 2.0 alpha is released. The links for download were not available directly on Mozilla.com website. Being Alpha, all features might not work and most of the plugins might not be compatible."
    This is about half a step above gibberish.
    --
    Slashdot: 24 hours behind every other site or your money back!
    1. Re:Is this the present or the past? by Anonymous Coward · · Score: 0

      above?

  8. Great job pushing out Bon Echo by suman28 · · Score: 2, Interesting

    I tried it on my computer. I didn't see any significant changes, and as others have pointed out, there was not much information on what exactly went into this release, but great job in making advancements.

    1. Re:Great job pushing out Bon Echo by dolphinling · · Score: 1

      Obviously you didn't actually try it. The entire bookmarks and history systems have been rewritten, backend and frontend. Tabs have changed slightly to improve UE for new users. Plenty of other things have changed as well. That's not "no significant changes".

      --
      There are 11 types of people in the world: those who can count in binary, and those who can't.
  9. idiiots? by Anonymous Coward · · Score: 0

    I have one for you:

    "bad" and "speller"

    and this is my first post on /.

    1. Re:idiiots? by Anonymous Coward · · Score: 1, Informative

      I have in mind a word that begins with "in" and ends with "on" --- it's not "inon"; it's "information"
      I also have in mind a word that begins with "informat" and ends with "formation" --- it's not "informatformation", it's "information".
      I hope that illustrates what "begins" and "ends" mean.

  10. Re:Looking forward to it by mumblestheclown · · Score: 3, Funny

    Karma whore +99999

  11. Why? by stubear · · Score: 1

    Why does each version of Firefox break plug-in and theme compatibility? I can maybe forgive SOME plug-ins but all of them? and THEMES!?!? WTF? There are plug-ins I used to use that ar still not compatible with 1.5. This is a MAJOR flaw with Firefox in my opinion. If you're going to tout the expandibility of Firefox as a major feature then youneed to make sure there's going to be at the very leat backwards compatibility for most plug-ins.

    1. Re:Why? by CockMonster · · Score: 0

      Poor design by not future-proofing code?

    2. Re:Why? by Anonymous Coward · · Score: 1, Informative

      this is probably because the themes/plugins themselves contain the version of firefox they should work for, and if the creator of the plugin does not set it higher than the current version, it will not work on the next. Usually they don't break, but because of this information, they won't even be started.

    3. Re:Why? by ajs318 · · Score: 1, Informative

      To be sure that they will work, you need to compile your extensions against the Mozilla source tree from which you compiled Firefox. That is not a limitation of any specific technology; rather, it is a limitation of mathematics. You have no more business expecting an extension compiled against 1.0.8 to work with anything except 1.0.8, than you have expecting that a CD will play on a cassette walkman.

      Now, if the extensions won't compile against the new source tree, you may need to patch them. Perhaps a variable or function has changed its name. Or a function might require an extra parameter. Read the changelog and get hacking, if you can't wait for your favourite extensions developer to do so.

      --
      Je fume. Tu fumes. Nous fûmes!
    4. Re:Why? by dolphinling · · Score: 4, Informative

      That would be the case... if Firefox extensions needed to be compiled. Which they don't.

      Extensions are programmed in Javascript and XUL, and for some advanced ones, XBL. They don't need to be recompiled, because they don't need to be compiled in the first place. The fraction of a percent that have more demanding interaction with the host system don't even necessarily need to be recompiled, depending on how they hook in to the mozilla code.

      You'd be right for other programs, but that's not how Mozilla works.

      --
      There are 11 types of people in the world: those who can count in binary, and those who can't.
    5. Re:Why? by Myen · · Score: 2, Informative

      Actually, the overwhelming majority of extensions are not even compiled. They're pure XUL/JS/CSS/RDF. The maxVersion arc mentioned in the sibling is the reason. It's used to guard against the browser internals changing under them - and yes, pretty much most of the things you can usefully change are considered browser internals. :( Then there's also the things randomly being ripped out (cf. the bookmarks and history going away and being replaced by "Places")

      And as long as you do no use frozen interfaces (including defining MOZ_STRICT_API, not defining MOZ_INTERNAL_API, and linking against XPCOM glue), it should work fine most of the time. It's just that, depending on what you want to do, that might not be possible ;)

    6. Re:Why? by Anonymous Coward · · Score: 0

      WTF are you smoking? There's no reason to expect an extension from 1.0.8 to not work. The version string that blocks about 99% of extensions on newer releases is a retarded feature. Nothing technical stops extensions from working except for a bit of over zealous design.

    7. Re:Why? by dolphinling · · Score: 1

      Some of your extensions will continue to work properly in new versions. Others will not. That gives you a choice:

      1. Disable them all
      2. Let them all keep running and have some of them work, and have others break the browser entirely because they interact poorly with new features

      Which do you choose?

      --
      There are 11 types of people in the world: those who can count in binary, and those who can't.
    8. Re:Why? by Anonymous Coward · · Score: 0

      Themes don't work because buttons get added/removed and the themes start to render incorrectly. There isn't much you can do about that.

    9. Re:Why? by Anonymous Coward · · Score: 0

      No see, you're missing the beauty of open source. We answer to no one...who needs backwards compatibity? That's for people who PAY for software.

      This is why OSS is doomed to fail in the long run.

    10. Re:Why? by EvanED · · Score: 1

      That is not a limitation of any specific technology; rather, it is a limitation of mathematics. You have no more business expecting an extension compiled against 1.0.8 to work with anything except 1.0.8, than you have expecting that a CD will play on a cassette walkman.

      Oh really?

      Perhaps then you can explain how programs written for *DOS* continue to work under XP without recompilation. Or how modern programs come with one exe, and not different ones for 95, 95osr2, 98, 98se, ME, NT3.5, NT4, 2K, XP, XP SP2, and 2003. Or how most binaries that ran on the IBM S/390 in 1970 or whatever still run on IBM's zServers today.

      It is CERTAINLY possible to make an ABI so that plug-ins could be compiled once and work for at least long periods of time. Might not be worth it, but it's certainly possible.

      Second, when you download a FF extension, do you see links for EVERY VERSION of Firefox? No! If I go to the Flashblock page, I have to choose between the 1.0 and 1.5 series browsers, but that's it. I don't have to choose between the release for 1.0.7 and 1.0.8. That alone pretty much destroys your theory.

      Third is what others have already said about why it works with FF in reality.

    11. Re:Why? by Anonymous Coward · · Score: 0

      I choose 2.

      Some _might_ work, and thats better than not even getting the chance to try.

      Its assumptions like yours that lead to the frustration being shown here. Basically - dont take my decisions to do something stupid away from me, i might just know better than you! It might break, it might not, you dont know any better than me.

      Why not compromise; disable them on first notice, but allow them to re-enable ("are you REALLY sure? no.. really - you might break something!")

      side note; "just hack the source and recompile" really isnt a decent answer for a mature product reaching a diversity of userbase.

    12. Re:Why? by dolphinling · · Score: 1

      I think you misunderstand... An extension can break the browser entirely: crashy, memory leaks, broken UI, even missing UI. And some of them will do this. If you don't believe this, try going and downloading old versions of extensions and hacking all of them to be enabled. You will not have a pleasant experience.

      --
      There are 11 types of people in the world: those who can count in binary, and those who can't.
    13. Re:Why? by DaggertipX · · Score: 1

      True true, regardless of this - dependencies don't just go away because code doesn't need to be compiled. For everyone who has a problem with Firefox extensions needing to be updated with new version number releases : go find me a plugin for, hrrm - lets say Outlook 2000, and tell me if it supports Outlook 2003 out of the box with no code changes or updates.
      Of the ones I've tried and used back from when I was on the MS Office bandwagon, they didn't seem to be forward compatible either, and I didn't expect them to. Maybe this has changed, but not to my knowledge.
      I'm just happy that the fact that this is open source gives me a workaround even if the developer doesn't update it, with closed source software I don't have that luxury.

    14. Re:Why? by DaggertipX · · Score: 1

      I've already responded to this argument here - http://slashdot.org/comments.pl?sid=180746&cid=149 57822, but I think it's an important enough one that I'll expand on it a bit more -

      It is bad practice to give users an easily accessible interface for destroying the application they are using. Every argument on slashdot ignores this principle, and I can't for the life of me fathom why. Properly made extensions should only break on major version number changes - and that is fine. That is good practice. If I have 11 extensions, and re-enabling one incorrectly tanks my browser, it doesn't matter if the other 10 are good.

      Everytime this discussion comes up, it's the early adopters who are frustrated by extensions not being updated as quickly as they would like. Here's another easy solution - wait for the major release branch to settle before upgrading - give extension developers time to respond to major changes.

    15. Re:Why? by lahvak · · Score: 1

      In this particular case:

      1) it is not even clear whether anything breaks. The submitter warns us that it *may* break, because it is alpha release.

      2) Even if things do break, it is to be expected. This is not even an alpha release, it is some random developer build that the submitter for some unknown reason calls an "alpha release". There is no reason for it to be compatible with anything at all, or even to do anything at all.

      In short, this summary is one of the most idiotic things submitted to slashdot I have ever seen.

      Now Firefox may have problems with backward compatibility, but it has nothing to do with this particular article.

      --
      AccountKiller
    16. Re:Why? by eyeye · · Score: 1

      Yeah that really fucks me off too, in fact I have pretty much given up on using extensions (except web developer toolbar at work) and themes because I got annoyed with backwards compatibility being broken.
      On the other hand FF now has enough features as standard that I don't really feel the *need* for extensions.

      --
      Bush and Blair ate my sig!
    17. Re:Why? by Anonymous Coward · · Score: 0

      I believe the grandparent poster is complaining about a real problem, but has attributed it to the wrong cause. I'd say there is actually a significant problem with API stability if extensions stop working when upgrading from 1.5 to 1.5.0.1. What I find even more amazing is that this compatibility problem even applies to themes, which a naive user would assume to just be a collection of bitmaps (.pngs or whatever). If only extension compatibility were just a problem of recompiling them, but many extensions (and themes) actually have to be modified to work with newer browsers.

    18. Re:Why? by luserSPAZ · · Score: 1

      The 1.0.x branch is a stable branch, that's why we don't have a different version for 1.0.7 or 1.0.8. And for a while we actually maintained one version that worked in 1.0.x and 1.5, but we decided to break backwards compatability for the sake of cleaner code in the extension. We have a separate branch now for 1.0.x and Seamonkey, which is why there are two versions available.

    19. Re:Why? by 42forty-two42 · · Score: 1

      If you mess with the UI, the elements the theme used to control may no longer exist, or the theme may fail to apply to all the needed elements. Thus, it's sensible to break themes over UI changes, to ensure someone will go in and check that the theme still works properly.

  12. Opera alternatives... by WIAKywbfatw · · Score: 2, Informative

    Opera 8.5: http://www.opera.com/download/

    Opera 9 Technology Preview 2: http://labs.opera.com/
    Weekly builds of Opera 9 TP2: http://my.opera.com/desktopteam/
    Changelog for Opera 9 TP2: http://snapshot.opera.com/windows/w90p2.html

    --

    "Accept that some days you are the pigeon, and some days you are the statue." - David Brent, Wernham Hogg
  13. Please don't ruin tabbed browsing... by urdak · · Score: 5, Insightful

    I can't believe that after Firefox actually implemented tabbed browsing *well*, people insist on ruining it in the name of "progress".

    The fact that firefox has just one "x" button that closes the current tab, rather then a close button per tab, is a *feature*, not a bug. Users of Lotus Notes, like myself, are all too familiar with what happens when each tab has a close button: you often click on the wrong one, and destroy the wrong tab! With Firefox 1.5's single tab close button, you can never accidentally close any tab: you can only close the tab you are now seeing.

    So I hope that if the "improvement" of having many close buttons makes it to FireFox 2, it will at least be configurable, so that users made miserable by the new feature could at least disable it.

    1. Re:Please don't ruin tabbed browsing... by chrismcdirty · · Score: 2, Interesting

      For people who insist on needing an 'X' per tab: middle click on the tab closes it as well. And usually fairly quicker than clicking the 'X' because it works anywhere on the tab.

      --
      It's like sex, except I'm having it!
    2. Re:Please don't ruin tabbed browsing... by WIAKywbfatw · · Score: 1

      Well, the best solution is to have both options and then let the user decide on which to use, which is exactly what Opera does.

      Tools > Preferences > General > Pages > Show close button on each tab.

      Personally, I have a close button on each tab. And, in Opera, if I do accidentally close pages that I still wanted to use then restoring them is easy: either a couple of mouse clicks or a keyboard shortcut later and your pages are restored, with their repective browsing histories intact.

      Just one of the myriad of reasons to love Opera.

      --

      "Accept that some days you are the pigeon, and some days you are the statue." - David Brent, Wernham Hogg
    3. Re:Please don't ruin tabbed browsing... by stony3k · · Score: 1

      Well it won't be so much of a pain, once the "Undo Close Tab" feature is implemented. IIRC, it should be a part of Fx 2.0 (not sure though).

      --
      Freedom is not worth having if it does not include the freedom to make mistakes. - Mahatma Gandhi
    4. Re:Please don't ruin tabbed browsing... by DrSkwid · · Score: 1

      I'm with you.

      I had the close on every tab through TabMix and I quickly turned it off, though with 'Undo Close Tab' the risk it mitigated.

      --
      There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
    5. Re:Please don't ruin tabbed browsing... by Apotekaren · · Score: 1

      I never use that button, I just click the tabs with my mousewheel. Just like I open new tabs from links by clicking the mousewheel. Webbrowsing has never been as easy.

      And yes, I hate the "close button in every tab"-idea, it's annoying, and disruptive in the IE7 Beta.

      --
      She: Hey, are you a traitor? Me: No, I'm atheist.
    6. Re:Please don't ruin tabbed browsing... by fritzk3 · · Score: 2, Informative

      You can also close a tab by right-clicking on it, and choosing "Close Tab." This works even if the tab that you want to close is not the one you're viewing.

      --
      All your sig are belong to us.
    7. Re:Please don't ruin tabbed browsing... by diogenesx · · Score: 1

      There is already an extension that adds a close button to each tab. Even it they made that design standard, I'm sure someone can write another extension to change it back to a single close tab button.

    8. Re:Please don't ruin tabbed browsing... by rbarreira · · Score: 4, Informative

      IE7 Beta 2 solves this by showing the close button in the tab, but only for the currently open tab - I'd say this is the second best solution after having the option on the preferences (which I haven't checked if IE has).

      --

      The AACS key is NOT 0xF606EEFD628B1CA427BEA93A9CA9773F
    9. Re:Please don't ruin tabbed browsing... by Myen · · Score: 1

      I believe (not certain on this) they may be considering just showing it on the active tab instead (though there's appearently problems with tab positions jumping around in that case).

      I also believe Tab Mix Plus might have an option to disable this. I know Too Many Tabs does (I currently have that installed); unfortunately the version I have randomly causes JS errors when opening/closing tabs, and I haven't managed to track it down enough to be useful to the author.

      Alternatively, just try setting the browser.tabs.tabClipWidth pref really, really small.

    10. Re:Please don't ruin tabbed browsing... by CastrTroy · · Score: 1

      Yeah, a "feature" like this should be able to be turned off, as all the extra close buttons take up extra space on my screen that I don't need. Also, Even with it on, I'd want an "unclose" tab feature, so that you can open a tab back up if you accidentally close it.

      --

      Anthropic principle: We see the universe the way it is because if it were different we would not be here to see it.
    11. Re:Please don't ruin tabbed browsing... by Anonymous Coward · · Score: 0

      It's not the best solution to have 10000 useless options to choose from. At least not in the GUI. I think opera is cluttered, And I wouldn't want firefox that way.

    12. Re:Please don't ruin tabbed browsing... by arekq · · Score: 3, Informative

      In Firefox trunk, the close button appears on every tab when there're only a few tabs. It appears only on the active tab when there're lots of tabs.

      Personally, I still prefer the behaviour in Firefox 1.5, where there's only one close button on the right. It's more efficient when I need to close multiple tabs. (aim, click, click, click vs. aim, click, aim, click, aim, click)

    13. Re:Please don't ruin tabbed browsing... by CastrTroy · · Score: 2, Insightful

      Am I the only one that finds clicking the mousewheel to be a stupid way of middle clicking. It's right up there with pushing on the control sticks in XBox/PS2 as a button. It's hard to push these buttons without having the scroll wheel/joystick move. Most people aren't even aware you can use these as buttons. I think if you're going to have a third button on the mouse, it should be a real button.

      --

      Anthropic principle: We see the universe the way it is because if it were different we would not be here to see it.
    14. Re:Please don't ruin tabbed browsing... by dolphinling · · Score: 1

      Having the close button on the tab is easier for new users. Having it where it was is easier for experienced users. A decision had to be made one way or the other, and it was made to favor new users, who probably wouldn't be able to find how to change it (or even know to change it), instead of the experienced users who will know how to change it.

      FWIW, I hate it, too. But the reasoning behind it is solid, so I understand I'll just have to deal until someone makes an extension.

      --
      There are 11 types of people in the world: those who can count in binary, and those who can't.
    15. Re:Please don't ruin tabbed browsing... by CastrTroy · · Score: 1

      If you're really looking for speed, don't even bother reaching for the mouse. Control-W works quite well for closing tabs.

      --

      Anthropic principle: We see the universe the way it is because if it were different we would not be here to see it.
    16. Re:Please don't ruin tabbed browsing... by Anonymous Coward · · Score: 0

      I'm with you.
      However, the Deer Park Alpha 2 (19 march nightly) *does* have a close button for every tab. And yes, it's annoying.

    17. Re:Please don't ruin tabbed browsing... by Tim+C · · Score: 1

      instead of the experienced users who will know how to change it.

      We will? Do you mean that it'll be hidden away inside about:config somewhere?

    18. Re:Please don't ruin tabbed browsing... by Greyfox · · Score: 1

      Or install one of the gestures plugins and use right-click mouse-wiggle to close a tab. I miss it when I have to work on other computers.

      --

      I'm trying to teach myself to set people on fire with my mind... Is it hot in here?

    19. Re:Please don't ruin tabbed browsing... by arekq · · Score: 3, Funny

      Well, I use ctrl-w, too. But there are times when my right hand is already on the mouse and my left hand is not on the keyboard...

    20. Re:Please don't ruin tabbed browsing... by arekq · · Score: 1

      I just took a visit to bugzilla. This "feature" is bug 308396.

      There's an extension called Tab No X to revert to the old behaviour.

    21. Re:Please don't ruin tabbed browsing... by WIAKywbfatw · · Score: 1

      Useless? Some people like it, some people don't: seems like a good reason to make it an option to me.

      Opera is cluttered? Really? Then why is it a smaller download with more core features (and better implemented ones at that) than Firefox?

      And, I have to ask, if a tickbox option in the Preferences isn't the place to put this sort basic option then where would be? Where would you put it so that it would be accessible to people looking for it?

      --

      "Accept that some days you are the pigeon, and some days you are the statue." - David Brent, Wernham Hogg
    22. Re:Please don't ruin tabbed browsing... by ubernostrum · · Score: 1

      I can't believe that after Firefox actually implemented tabbed browsing *well*, people insist on ruining it in the name of "progress".

      You're absolutely right, you know. Having a close button on every tab completely removes or negates absolutely every single benefit of tabbed browsing, without hope of recovery.

      Or not. People seem to use Safari, Opera, Galeon, and other browsers that do this, so maybe it's not quite the "ruins tabbed browsing" problem you think it is...

    23. Re:Please don't ruin tabbed browsing... by Bushwuly · · Score: 1

      Maybe it's just me, but what would make it so you "often click on the wrong [tab]"? I've been using Tab Mix Plus for Firefox for almost a year, and with close buttons per tab I've never closed the wrong tab. The active tab is in bold, and since at least Tab Mix Plus 0.3.0.3 you can color the text of unread tabs.

      Part of the reason I sought out such a solution for Firefox was because of the single close tab; you had to either select the tab you wanted to close before hitting the button, or right-click the tab and select close from the context menu. Why not have a readily seen solution?

      If anything, recognize that others browse differently than yourself. The least Mozilla can do is make it a native option for the user's choice.

      --
      Get over yourself.
    24. Re:Please don't ruin tabbed browsing... by Bushwuly · · Score: 1

      Reading everyone's comments on this topic, I wonder: how many tabs do you keep open? I can't think of a time where I had any more than 10 open at one time, and I've always been able to see at least some of the text on each of them...

      --
      Get over yourself.
    25. Re:Please don't ruin tabbed browsing... by Anonymous Coward · · Score: 0

      But there are times when my right hand is already on the mouse and my left hand is not on the keyboard...

      TMI. TMI.

    26. Re:Please don't ruin tabbed browsing... by FuzzyBad-Mofo · · Score: 1

      Am I the only one that finds clicking the mousewheel to be a stupid way of middle clicking.

      Yep, it's just you. And the guy who modded you up, I guess.

    27. Re:Please don't ruin tabbed browsing... by porneL · · Score: 1

      If your hands are well trained, you can use mouse gestures.

    28. Re:Please don't ruin tabbed browsing... by Anonymous Coward · · Score: 0

      Nope, I agree with you. I never use the wheel as a button. I love the wheel to scrol pages, though don't get me wrong.

    29. Re:Please don't ruin tabbed browsing... by eyeye · · Score: 1

      Am I the only one that finds clicking the mousewheel to be a stupid way of middle clicking... It's hard to push these buttons without having the scroll wheel/joystick move

      Either you have a crap mouse or a neurological problem.
      --
      Bush and Blair ate my sig!
    30. Re:Please don't ruin tabbed browsing... by Haeleth · · Score: 1

      Am I the only one that finds clicking the mousewheel to be a stupid way of middle clicking.

      No, it's not just you. But then I use one of the wireless Intellimouse Explorers where the mousewheel is so stiff that it's almost impossible to click without turning it.

      So what I do is remap one of the thumb buttons on the side to act as button 3. It's surprisingly comfortable and convenient. (The other thumb button is so far forward that it's totally useless, but there you go.)

    31. Re:Please don't ruin tabbed browsing... by CastrTroy · · Score: 1

      I Have a Micosoft explorer trackball that has 5 buttons. I use the 4th and 5th for copy and paste. Works really well. I don't think I've ever found the third button that useful for much, so I don't really need to use it.

      --

      Anthropic principle: We see the universe the way it is because if it were different we would not be here to see it.
    32. Re:Please don't ruin tabbed browsing... by Ex+Machina · · Score: 1

      Obviously you are not looking at shitty free pornography enough!

    33. Re:Please don't ruin tabbed browsing... by heinousjay · · Score: 1

      Useless? Some people like it, some people don't: seems like a good reason to make it an option to me.

      It is an option, using the system called 'Extensions.' Not as convenient as a tickmark on a panel, I admit, but available for people who want it.

      Opera is cluttered? Really? Then why is it a smaller download with more core features (and better implemented ones at that) than Firefox?

      Ehhh... better implemented features is an opinion, so I'll sort of dismiss it (particularly since I disagree). As for the rest: different implementation technique. Opera forms the basis of Opera. Firefox is built on the root of an application foundation that forms the basis of a number of products, not all of which are browsers.

      --
      Slashdot - where whining about luck is the new way to make the world you want.
    34. Re:Please don't ruin tabbed browsing... by Omestes · · Score: 1

      I concur.

      My middle button (on OS X) is mapped to expose all windows, which is a very nice feature for switching between windows, much more convenient than hitting F9, meaning its functionality is killed in FF.

      Though it would be nice if there was an easy way to kill a tab, outside of of ctrl-w. A nice single click solution...

      --
      A patriot must always be ready to defend his country against his government. -edward abbey
    35. Re:Please don't ruin tabbed browsing... by Anonymous Coward · · Score: 0

      > It's more efficient when I need to close multiple tabs. (aim, click, click, click vs. aim, click, aim, click, aim, click)

      Install a decent extension like Tab Mix Plus and just middle-click the tabs to make 'em go away. If you mis-click, you just middle-click in an empty area and it comes back.

    36. Re:Please don't ruin tabbed browsing... by neafevoc · · Score: 1

      Thanks for the tip.

      Of course, I first chose not to believe you. And I had to choose this particular tab to close. Suffice to say that your tip definitly does work properly.

    37. Re:Please don't ruin tabbed browsing... by ChronoReverse · · Score: 1

      I've mapped one of the buttons on my MX310 to ctrl+F4 which closes tabs nicely =)

    38. Re:Please don't ruin tabbed browsing... by darrylo · · Score: 1

      This is bloat.

      Whatever happened to extensions?

      If people really want this questionable functionality today, I suggest they try out the "Tab Mix Plus" extension. (Actually, I recommend that they install this extension anyway, because it provides so many other useful features, besides the questionable, "Close tab X" on each tab. Among other things, it provides session saving/remembering, and the ability to UNDO closed tabs. Good stuff, but keeping undo history around does suck up memory.)

    39. Re:Please don't ruin tabbed browsing... by anti-trojan · · Score: 1

      Middle-click already closes tabs without needing any extensions.

      They don't come back as you described, though.

    40. Re:Please don't ruin tabbed browsing... by 1110110001 · · Score: 1

      I can't believe that after Firefox actually implemented tabbed browsing *well*, people insist on ruining it in the name of "progress".

      They already ruined it for me as a Mac user. In 1.5 they disabled ctrl+tab and the only way to get it back is patching tabbrowser.xml in one of the jars. And that needs to be done after every update. There isn't even a hidden preference or anything - altough I submitted the code for it.

    41. Re:Please don't ruin tabbed browsing... by alexburke · · Score: 1

      Am I the only one that finds clicking the mousewheel to be a stupid way of middle clicking. It's right up there with pushing on the control sticks in XBox/PS2 as a button. It's hard to push these buttons without having the scroll wheel/joystick move.

      I'm willing to bet you have a Microsoft mouse made in the last year or two. Microsoft used to have detents in their scroll wheel, but they made a deliberate decision to remove them, with which I disagree.

      My Logitech MX610 (like all Logitech mice, and like the Microsoft ones that were worth owning) has nice detents in the wheel, and it's very easy for me to click the scroll wheel without rolling it (or even tilting it sideways, since it can do that -- or at least it could if I had the Logitech drivers installed, which I don't, since all buttons other than the IM button work perfectly in XP without them).

      How's THAT for a run-on sentence? :)

  14. Re:Looking forward to it by DrSkwid · · Score: 1

    Who's idea do you think the Ping attribute is ?

    --
    There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
  15. having developed extensions for FF... by Alphager · · Score: 5, Informative

    .. i can tell you that there is one thing that "breaks" most extensions: In the extension, you can specify a maximum version number under which the extension works. Normally, the extension developer sets it to a version he has personally tested (the actual release). Whit each version-bump, he retests and changes just the maximum version-number. If you want to do it yourself: get into the manifesto of the extension and search for this String "1.5" and replace 1.5 with a higher number.

    1. Re:having developed extensions for FF... by Myen · · Score: 1

      Specifically, search for the XML tag "maxVersion" in the http://www.mozilla.org/2004/em-rdf# namespace (usually written as <em:maxVersion>).

      Or just get Nightly Tester Tools.

      (Not linking because, AFAIK, his server was badly slashdotted last time it was mentioned in a comment. If you really want to, Google.)

    2. Re:having developed extensions for FF... by Alphager · · Score: 1

      thanks for posting that, Slashcode ate the tag.

    3. Re:having developed extensions for FF... by user24 · · Score: 1
      In the extension, you can specify a maximum version number under which the extension works
      ... and I *wish* that when installing extensions, FF would give me an option to override the developer's choice.

      Yes, I know, rename the xpi to .zip (once you've re-downloaded it), open install.rdf, change the version number, put it back into the zip at normal compression, rename back to .xpi and open in FF... how about a simple "I don't give a crap that the developer says this extension won't work in 1.5. I wanna see" button

      I think it's useful for the developer to be able to say; "will only work in versions greater than x.y", but surely it's impossible for an extenion author to say that their extension won't work in a version of FF that doesn't exist yet, which is effectively what the maxVersion allows them to do. It's ridiculous. When I upgraded to 1.5, I had to spend ages tediously hacking all my extensions so they'd work with 1.5. There was nothing inherent in the functionality that made them break, just some arbitrary maxVersion crap - gimme an override button!!!
    4. Re:having developed extensions for FF... by Alphager · · Score: 1

      File a bug about it. Mark it as wishlist-bug and hope that it gets picked up.

    5. Re:having developed extensions for FF... by croddy · · Score: 1
      surely it's impossible for an extenion author to say that their extension won't work in a version of FF that doesn't exist yet
      surely it's *more* impossible to say that an extension *will* work with a version of firefox that doesn't exist yet. the nightly tester tools include an option to override that.

      what are you so mad about again?

    6. Re:having developed extensions for FF... by user24 · · Score: 1

      well, maybe with major version changes, but the majority (if not all) of the extensions that "didn't work" in 1.5 only didn't work because of the maxVersion field.

      I'm not suggesting that a developer should state that their extension either *will* or *will not* work in any given future version of FF. What I'm suggesting is that extensions should have a minVersion, and a maxVersion, but if the version of FF that you're installing the extension on exceeds the maxVersion of the extension, FF should notify the user that "this extension was not designed for this version of Firefox. If you'd like to take your chances and install it anyway, click install, but remember that it might work unexpectedly or not at all. Otherwise, click cancel", rather than just saying "too bad buddy, the developer says his extension won't work in this version, though he can't possibly have known that when he wrote the extension" which is effectively what it does at the moment.

      Again, I'm mad that I have to piss about editing extensions that would work perfectly well except that they think they won't work.

    7. Re:having developed extensions for FF... by user24 · · Score: 1

      the majority (if not all)*

      * of the ones I used. Obviously there are some that really didn't work.

      Just browsing through the list of extensions at tinyurl.com/cjhbh, there's plenty that have a new version which simply says "incremented maxVersion for 1.5". I think this kinda proves my point.

  16. Advantages? by zaguar · · Score: 1
    Are there any advantages to upgrading? On the down-side, I can see

    1: Losing compatibility with extensions
    2: Losing stability/higher memory usage (come to think of it, this isn't really a change)
    3: Bugs galore - possible security issues?

    So, is there any reason for anyone to use this until a release candidate comes out?

    --
    "Sure there's porn and piracy on the Web but there's probably a downside too."
    1. Re:Advantages? by bunratty · · Score: 2, Informative
      There are two reasons I can think of:

      1. Mozilla puts the release out so users can report bugs. Unless you already have a Bugzilla account, I suggest you wait until a release candidate is out.
      2. If Firefox 1.5.0.1 is crashing so often or leaking memory so badly for you that you need to restart Firefox every day or so, you might want to try 2.0 Alpha to see if it fixes your problems. Of course, if it doesn't you should report the problem (see #1).

      End users generally should not be downloading alphas because of the downsides you mention.

      --
      What a fool believes, he sees, no wise man has the power to reason away.
    2. Re:Advantages? by FooAtWFU · · Score: 1
      Reasons? Yes, just a few.

      1) You're helping Mozilla.org find bugs.
      2) Because you can.

      --
      The World Wide Web is dying. Soon, we shall have only the Internet.
    3. Re:Advantages? by mlefevre · · Score: 1

      There's reason for some people to use it - otherwise who is going to find and fix the bugs, or make the extensions compatible?

      But for most users, there is no good reason for them to switch. This will be (it's not actually released yet) a release aimed at developers. In particular, for developers who want to try out the new bookmarks/history back-end stuff.

      I certainly can't think of a good reason for posting on slashdot about an alpha release that's not even released yet...

    4. Re:Advantages? by grand_it · · Score: 2, Informative
      1: Losing compatibility with extensions
      2: Losing stability/higher memory usage (come to think of it, this isn't really a change)
      3: Bugs galore - possible security issues?

      Repeat after me:

      1 Compatibility issues are *normal* in alpha software. That's what they release it for: to find problems.

      2 You *shall not* evaluate stability, performance nor memory usage in an Alpha stage software. Jeez, it has debugging code in it!

      3 You *shall not* install Alpha or Beta software in a production environment, or on machines whose security might be at risk.

      Karma whoring wikipedia entry about developement stages here.

  17. Do people even know what "alpha" release means? by Anonymous Coward · · Score: 0

    Alpha means that there are missing or partially implemented features that are planned for the final release.

    Beta means it's fully implemented and feature complete but may contain bugs or need tweaking.

    Sheesh... And the 1.2.3.4.5.6.7 release numbering that so many open-source projects are using is totally retarded. Hell, I saw some project the other day that was a x.x.x+1 release that was API incompatible with the previous release! Morons. Nobody does versioning correctly and they tack on extra dot versions because they are improperly managing releases.

  18. Portable Firefox 2.0 Alpha by thedude13 · · Score: 2, Informative

    There's a "portable" version available here:

    http://www.cybernetnews.com/?p=411

    Definitely a plus b/c it let's you avoid dealing w/profile incompatibilites/conversion between the different versions of firefox and instead stores it in the directory with the portable firefox program

    1. Re:Portable Firefox 2.0 Alpha by SirDaShadow · · Score: 2, Insightful

      Sir, you just made my day. I already had portable FF 1.5. All I did was copy the profile folder to the 2.0a1 one, and presto...all settings...all extensions were migrated. Of course, to make them "compatible" I had to use Nightly Tools Extension. The only one that "broke" so far was tabbrowser extensions, and I'm sure it's going to be updated pretty soon...

    2. Re:Portable Firefox 2.0 Alpha by SirDaShadow · · Score: 1

      meh...I'm having issues...it works perfectly from a folder on the c drive...when I move the folder to my portable drive it refuses to work/extensions will not load/they will become disabled/other ill side effects....

  19. MNG, Javascript 2.0 by ObsessiveMathsFreak · · Score: 1

    What I would like to see in 2.x is some MNG support. It's about time people moved away from animated GIFs as the situation is rapidly getting out of hand. On some forums, animated sig images can be up to 500KB in size. There's demand for a better animated standard, and why MNG support was dropped from Firefox 1.5 is beyond me.

    Also, Javascript needs an overhaul. If XUL is ever going to take off, it can't rely on a language that doesn't even have a "class" keyword or equivilent.

    It would be nice if the Mozilla foundation took it upon itself once more, to drag the rest of teh industry, kicking and screaming, into the future.

    --
    May the Maths Be with you!
    1. Re:MNG, Javascript 2.0 by Anonymous Coward · · Score: 0

      JavaScript doesn't need a class keyword or equivalent. It is already a full OO language, it just happens to be very much unlike C++.

    2. Re:MNG, Javascript 2.0 by dolphinling · · Score: 1

      Javascript 2 is being worked on. (You may want to look around more, that's just the first thing I found.)

      MNG wasn't "dropped" from Firefox 1.5, it was never even planned on being included. It hasn't been included in Mozilla since (IIRC) Mozilla 1.3, years ago. However, I was looking at it just yesterday, and the code is getting constantly smaller and better, so hopefully it will be included in Firefox 3.0 (planned, IIRC, for around a year from now).

      --
      There are 11 types of people in the world: those who can count in binary, and those who can't.
    3. Re:MNG, Javascript 2.0 by Myen · · Score: 1

      You may want to go read news://news.mozilla.org/mozilla.dev.general in the giant 2006-02-27 thread. I *think* somewhere in there somebody mentioned that, no, MNG isn't going to be in Mozilla until hell freezes over or something.

      I think it may be around msgid: CuidnYb3aINfhIvZ4p2dnA@mozilla.org but I'm not sure - I read that part a few days ago.

    4. Re:MNG, Javascript 2.0 by Anonymous Coward · · Score: 0

      "why MNG support was dropped from Firefox 1.5 is beyond me."

      IANAFFD but it's probably got something to do with not wanting to imiplement it then have to RE-implement it for FF3's switch to the Cairo rendering system.

    5. Re:MNG, Javascript 2.0 by Fittysix · · Score: 1

      Personally I'd like to see APNG gain support to the point it becomes worthwhile to add it into the code.

      --
      *.sig
    6. Re:MNG, Javascript 2.0 by Blakey+Rat · · Score: 1

      Say I wanted to make a MNG file, what program would I use to do it?

    7. Re:MNG, Javascript 2.0 by Glenn+R-P · · Score: 1

      There is a list of MNG-supporting applications at
      http://www.libpng.org/pub/mng/mngapps.html

  20. Experimental build by gerbalblaste · · Score: 1, Informative

    So far the only distinctive feature of this is that it breaks extensions and will not load book marks.
    As far as i can tell this gentleman went looking through the firefox ftp site and stumbled upon this. Its a Tinderbox build. meaning its increadably unstable and is just a starting point for further code development.

  21. Editors, do your job! by dmbtech · · Score: 1, Insightful

    You MUST wait for an official announcment before announcing all over the media (/.) than an alpha has been released when it really hasn't. I really suggest you change that announcment editors and say something like update "Not really released". You can't just go reading a blog and think that is news. People, DO YOUR RESEARCH!! Alpha 1 HAS NOT BEEN RELEASED!

    1. Re:Editors, do your job! by Anonymous Coward · · Score: 0

      maybe software shouldn't be posted to mirrors before it is released

  22. No Quicktime plugin for Linux! by Anonymous Coward · · Score: 1, Interesting

    I got an opportunity to try the latest Firefox (1.5.0.1) with the Tomahawk Desktop. For those who are wondering what is Tomahawk Desktop, it's an Apple like Multimedia Linux OS for desktops and laptops.

    I have noted the Firefox is called Deer Park! Is there a name change again?

    I further noted I cannot browse http://www.apple.com/aperture/ because there is no Quicktime plugin for Firefox on Linux. It seems Apple doesn't release a Quicktime plugin for Linux, like no iTunes for Linux. Can this issue be resolved at least with the Firefox 2.0? Is Quicktime a closed specification? Why doesn't Mozilla Foundation officially ask the specification from Apple rather than waiting forever? Is there a solution already under way to fix this issue?

    1. Re:No Quicktime plugin for Linux! by Lussarn · · Score: 1

      It would be easier to get everybody to stop releasing quicktime content than to get Apple to release a quicktime player for Linux/Unix. In the meantime you can install Mplayer plugin.

    2. Re:No Quicktime plugin for Linux! by Yaotzin · · Score: 1

      No, there's not a new name change. Versions of Firefox that are not yet officially released are called "Deer Park".

      --
      Error: No error occurred
  23. "all features might not work" !?! by Anonymous Coward · · Score: 0
    Being Alpha, all features might not work
    That would be a pretty horrible alpha, if none of the features are working. Surely you mean "not all features may work".

    Also
    and most of the plugins might not be compatible.
    Don't you mean to say that "SOME of the plugins might not be compatible"?

    Since 2.0 is still build from the same branch as 1.5, as far as i've been following the Firefox/Gecko developments no deeply rooted changes were made to the way plugins are handled, so i don't expect you'll be experiencing any problems in THAT department.
    1. Re:"all features might not work" !?! by EvanED · · Score: 1
      That would be a pretty horrible alpha, if none of the features are working.

      It would. But that's not what the sentence says. Read again:

      Being Alpha, all features might not work


      In other words, all features have a chance of not working. Or every feature has a chance of not working.

      I'll agree that it's awkward wording, but you're trying to be pedantic to the point of being wrong.

      Don't you mean to say that "SOME of the plugins might not be compatible"?

      Hey, (s)he could have written "ALL of the plugins might not be compatible" and still been fine even if all plugins worked.
    2. Re:"all features might not work" !?! by Myen · · Score: 1

      They obviously mean extensions (*.xpi, install.rdf) instead of plugins (NPAPI).

      Unless they mean the already-broken superceded Adobe SVG viewer that used unfrozen interfaces... (Later versions of the SVG plugin are not scriptable becuase Adobe could not implement that without using those unfrozen interfaces and basically being horribly tangled in Mozilla internals that might crash in the Mozilla release after that)

      And extensions will break - at least, any that deal with bookmarks and history. What with the coming of Places :p

    3. Re:"all features might not work" !?! by Anonymous Coward · · Score: 0

      Well, the other AC DOES have a point. It's an alpha product, so sure, some things may not work as intended, but it WOULD be a horrible alpha if nothing worked ;)

      I guess s/he was not pedantic, but merely pointing out that the way the article was worded it was a rather obvious statement that goes for any alpha or beta product.

      As to the second point about plugins. As someone else said: they probably meant "extensions" rather than ""plugins".

      As pedantic as AC may sound to you, it in the end does more damage to have disclaimers that are grammatically correct but are so broad that they don't mean anything anymore.

  24. Re:Looking forward to it by wwmedia · · Score: 2, Insightful

    At least with an open source project you know they're not going to go crazy adding features to please the marketing droids.



    what about google and firefox being in same bed?

    doesnt mozilla bend over backwards over googles millions? http://slashdot.org/article.pl?sid=06/03/11/053924 5

    oh and last i checked google are making billions from marketing :)

    so to put the 2 together

    THEY ARE going crazy adding features to please the marketing droids

  25. Re:Looking forward to it by _Hiro_ · · Score: 1

    Well, if it's not stable for you, could you list the bugs and issues you're having?

    Either here or in the Firefox Bugzilla would be great, and don't forget your TPS cover sheet!

    --
    -Pope Peter Porker, S.O.W., K.M.K.R., U.G.O.A., F.S.G.S.D.
  26. Wow, quite the fuss... by Zitchas · · Score: 2, Informative
    Now, I'd expect this amount of excitement over, say, a BETA release, but for an Alpha? Why bother? I like checking out new things and having the latest and greatest, but I think I'll wait for one that the developers at least hope will be functional enough to release. I'm not a developer, I don't need to be digging out a Tinderbox version to satisfy my needs.

    Oh, and for informational purpsoses:

    Firefox = official public release

    DeerPark = developer's copies, optimized and/or individualized bulids, and all those other builds that aren't the official issued-for-the-general-public builds. Which, it would stand to reason, would include all the alpha and beta builds.

    --
    Z
  27. Just like Emacs by Anonymous Coward · · Score: 0

    Just like Emacs...a nice clean text editor. It doesn't have crazy features like the ability to play tetris, check your email, manage your calander, etc. etc.

  28. But isn't this all open source? by sgant · · Score: 1

    Isn't this all a community written thing? Can't someone just take all the source-code and say "It's released"? This is my version of the released Firefox.

    Mozilla.org isn't holding any code back are they? I thought everything was out in the open...everything had to be released as it's being worked on and anyone can contribute and re-write anything they want with the source.

    So how can they say "When WE make a new release, WE'LL say so"? I mean, who are they to say anything on what happens to this open code?

    I'm not trying to be a troll here or start anything, but obviously I'm VERY uninformed about how this all works.

    --

    "Leo Fender was in a 'state of grace' when he designed the Stratocaster." -- Paul Reed Smith
    1. Re:But isn't this all open source? by Bohiti · · Score: 3, Informative

      It's called quality assurance. There needs to be someone in charge to avoid the scenario you describe: someone takes a buggy pre-alpha nightly, and distributes it as "Firefox 2.0".

      That would obviously be devastating for the project. I'm glad Mozilla.org is in charge, albeit the only thing really preventing the previous scenario is community respect.

    2. Re:But isn't this all open source? by Kjella · · Score: 4, Insightful

      Isn't this all a community written thing? Can't someone just take all the source-code and say "It's released"? This is my version of the released Firefox.

      First off, the source code is there. But claiming it is a release (as in Mozilla.org's) when it is not is just misinformation. A minimum of honesty in advertising would say you've made your own fork of Firefox.

      Secondly, you don't need to give out source unless you give out binaries. So you could (though this is only realistic on smaller projects or those controlled by one company) say "When we make a new release, we'll release the source". I think Apple did that with their Safari browser.

      Third, the GPL doesn't change trademark law. You can take the code, but you can't release under the same trademarked name. You can make a clone like CentOS is of Red Hat Enterprise Linux, but you can't release under the name itself.

      So when YOU make a release YOU'LL say so (presumably under another name, since Firefox is trademarked). It only gets stupid when other people is making release statements on behalf of someone else.

      --
      Live today, because you never know what tomorrow brings
    3. Re:But isn't this all open source? by Anonymous Coward · · Score: 0

      All the code is out in the open, but that's not everything. In particular, the Firefox name and logo are trademarks.

      So there's nothing stopping anyone grabbing the source, changing the name and releasing it. But then it'd be Fred's Acmebrowser 1.0 alpha rather than Mozilla Firefox.

      Also, people can change anything they want in their own copy of the code, and release it however they want. But the copy of the source code held by the Mozilla folks is controlled, and they don't have to let just anyone change things.

      As it happens, Mozilla (like lots of open source projects) is quite open about lots of things. But it's only the source code that's made open by the license.

    4. Re:But isn't this all open source? by Anonymovs+Coward · · Score: 4, Informative
      So how can they say "When WE make a new release, WE'LL say so"? I mean, who are they to say anything on what happens to this open code?

      You're welcome to make a release, but you can't call it Firefox. Firefox is a protected trademark, as is Mozilla.

      Besides, that's not what the article said.

  29. Nightly from 19 march says "Deer Park Alpha 2" by Anonymous Coward · · Score: 0

    I'm running the nightly from 19 march, and it says "Deer Park Alpha 2". So, am I running this unreleased alpha 2.0 version?

    Anyway, it runs OK (well enough to post this comment), but has crashed on my once already today, however, this was when clicking on a link on a site that firefox 1.5 simply wouldn't accept (didn't do anything when clicking on the link).

    Also, the cursor is sometimes one place more to the left than it should be, a bit annoying when posting this story:)

    (Oh, and windows warned, "This software may harm your computer", but then again, it always says that).

  30. Re:Looking forward to it by DrSkwid · · Score: 1

    Wow, some links from the article *I* linked to.

    They still don't explain WHOSE idea the Ping attribute was, or offer a compelling reason for its inclusion, particularly as it is something you can already do with onclick, as I mentioned here

    W3 is a LOT of organisations : http://www.w3.org/Consortium/Member/List

    --
    There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
  31. another reason to go with opera by monkbent · · Score: 1
    By default there is a trashbox that saves the content of all closed tabs. Close the wrong one? Not a problem - just click on it in the trashbox, and it is restored along with its full history (and it's not a memory problem either, as Opera actually uncerstands the idea of a small footprint).

    One other Opera tab feature is what always keeps me coming back - when you close the tab you are in, you revert to the last tab you were viewing instead of the tab next door. This fits my surfing pattern perfectly (which is to open relevant links in the background, read them, then return to the main page). For me, it's the killer feature of Opera. Maybe it's available as an extension, but that alone with so many other small things keep me here (and Opera 9 has fixed any rendering problems I had been having).

  32. Also remove the "close other tabs" context menu by wysiwia · · Score: 1

    I always use the context menu to close a tab with the mouse, yet I have to be carefully to not choose the "close other tabs". Besides the "close" in the contect menu should be the very first command.

    O. Wyss

    --
    See http://wyoguide.sf.net/papers/Cross-platform.html
  33. Move along please by Madcowz · · Score: 1

    A news story about an Alpha version which doesn't even exist.

    Cor, that's entertainment!

    /Mad

  34. Whoa Mozilla by TheSkepticalOptimist · · Score: 1

    I mean, this is an organization that used to offer product releases of .001 increments over the course of years, now they went from 1.0 to 1.5 and already talking about 2.0 versions of Firefox.

    Is Mozilla looking to become Microsoft?

    Slow and steady is what has founded Mozilla and Firefox, don't blow it by having version upgrades that coincide with the frequency of changing underwear.

    --
    I haven't thought of anything clever to put here, but then again most of you haven't either.
    1. Re:Whoa Mozilla by AlXtreme · · Score: 1
      Is Mozilla looking to become Microsoft?
      You mean, they're jumping from 95 to 2000?

      Really, what are you smoking? I could use some of that...

      --
      This sig is intentionally left blank
    2. Re:Whoa Mozilla by Fittysix · · Score: 1

      Well, I'd like to see microsoft offer Nightly builds of the latest checkins

      --
      *.sig
    3. Re:Whoa Mozilla by luserSPAZ · · Score: 1

      It will be almost a year between the 1.5 and 2.0 releases. How much slower would you like it? Given that IE7 will be out soon, what's the value in waiting? There was plenty of project management that went into the decision to release 2.0 and 3.0 at their respective times.

  35. A close button on each tab is a BAD idea by jdoire · · Score: 1

    A close button on each tabs is indeed a bad idea, not only does it take extra space, but also it takes extra time to find which "x" should be pressed.

    Opera uses an "x" button on each tabs and I sure hate it, everytime I want to close a tab I find myself searching for a few seconds which "x" I need to click and to make sure it is the really the right one.

    1. Re:A close button on each tab is a BAD idea by Vr6dub · · Score: 1

      Or just take the close buttons out all together. If your using a mouse (instead of a touchpad) the quickest way to close a tab in Opera is to hold your right mouse button and make a upper case L shape. You can do this anywhere on the current page.

    2. Re:A close button on each tab is a BAD idea by jdoire · · Score: 1

      Good suggestion! I tried the mouse gestures, and I liked it! :)

      Still, I think that a "x" on each tab is a bad idea.

  36. The only new "features" we really need by Anonymous Coward · · Score: 0

    The Firefox developers should honestly not write another line of new code until they finally fix:

    - the memory leaks in the browser that have been going on forever

    - the browser periodically sucking up CPU usage

    Yes, you can blame some of these on poorly written extensions ... but not all of it. And as the memory and CPU usage is attributed to Firefox, I consider Firefox responsibile. As these extensions are basically XUL/Javascript, Firefox should totally manage its extension sandbox in a much better manner (i.e. throttling CPU usage, memory allocation, etc.).

    I love Firefox, but every now and then I consider migrating back away from it as my primary browser for these two issues alone. I can write an extension to overcome Firefox's shortcomings in many areas, but this is core and needs to be addressed as such. If you look at Bugzilla for Firefox, you can see these reported many times - but the developers always seem to shrug these off as not important or not reproducible. I know these are much harder and less fun to deal with than flashy new features, but it is all part of putting out a quality product.

    1. Re:The only new "features" we really need by uncqual · · Score: 1
      I too have been tempted on several occasions to go stop using FF due to the memory leaks and excessive sporadic CPU usage. Yep, it's probably the extensions, but FF w/o extensions is like a hug without a kiss when you're looking for a bit more than just a kiss [note to self - consider submitting preceding analogy to annual /. bad analogy contest].

      The relatively recent addition of the annoying "A script on this page is running slowly and driving you nuts. Nope, I'm not going to tell you which one, but would you like to continue or cancel it?" dialog was a pretty sad admission of surrender (I get it almost every time I "open in tabs" from my bookmark toolbar with my "important" eight web sites). Upon getting this dialog, I went poking around looking for the "what constitutes too slow" (or whatever the term they use is) in order to make it less picky (or disable it entirely), but found no knobs to turn in the obvious places (tools->options) before I gave up looking in disgust (yep, there may be a setting for it in about:config, but I was too disgusted to search for it).

      I'd be really happy if FF would show me how much memory (current & peak) and how much CPU time each extension had "used" so I could decide which of my 25 extensions to nuke. Maybe this is technically difficult to do, but at this point FF has enough features to make spending time on usability issues appropriate.

      --
      Why is there an "insightful" mod and why isn't it "-1"? If I wanted insight, I wouldn't be reading /.
  37. Article should be removed. by cparker15 · · Score: 1

    Hey mods, can we get this removed from the FRONT PAGE and/or deleted? Thanks!

    --
    Have you driven a fnord... lately?

    You must wait a little bit before using this resource; please try again later.

  38. Re:Please don't ruin tabbed browsing...get exts! by ramsj900 · · Score: 1

    Sounds like you need the 'session-saver' extension https://addons.mozilla.org/extensions/moreinfo.php ?application=firefox&category=Tabbed%20Browsing&nu mpg=10&id=436/ so if you close or crash Firefox you can pick up where you left off. A.K.A. lifesaver for a die hard wanderer. If that is too much for you, try this extension that removes the little enticing 'x' for closing tabs from your life. https://addons.mozilla.org/extensions/moreinfo.php ?application=firefox&category=Tabbed%20Browsing&nu mpg=10&id=2092/

    --
    Relax, aren't you lucky that it is only my Opinion?
  39. It's out by Anonymous Coward · · Score: 0

    Its out here's the link! http://lookleap.com/ftp.mozilla.org/a1

  40. Re:Looking forward to it by Vr6dub · · Score: 1

    Just to add my .02, I switched to Opera and haven't looked back. They both are efficient browsers that do their job well. What sold me on Opera were the mouse gestures. I understand there are programs that will give you this functionality but I found them to be buggy and each program had different command strokes (pluse it's one more piece of software running in the background). Talk about intuitiveness and efficiency, gestures will really speed up your browsing. I can manipulate tabs with great ease now that I am familiar with all the different commands.

  41. Thanks guys for explaining this all. by sgant · · Score: 1

    I'm not a developer as you can all see...and thanks for enlightening me about all this. Very interesting.

    --

    "Leo Fender was in a 'state of grace' when he designed the Stratocaster." -- Paul Reed Smith
  42. Re:Redundant by WIAKywbfatw · · Score: 1

    Oh, how bitter and twisted we are. Got something against choice?

    People like you make me laugh, you really do. You are aware that 90 percent of the features that are supposed to differentiate Firefox from Internet Explorer were borrowed (or, to put it more directly, copied) straight from Opera?

    And, by the way, since when did popularity imply quality?

    --

    "Accept that some days you are the pigeon, and some days you are the statue." - David Brent, Wernham Hogg
  43. Mod parent off-topic by Anonymous Coward · · Score: 0

    Not an opera article.

  44. Thru? by xx_toran_xx · · Score: 1, Insightful

    So what, is slashdot like myspace now?

    You could at least bother to change "thru" to "through."

    --
    Arrrrrrr
  45. Hopefully.. by loic_2003 · · Score: 1

    With a little luck, they'll finally get rid of the hugely irritating copy+paste bug that still seems to be lingering about...

  46. Re:Looking forward to it by ubernostrum · · Score: 1

    They still don't explain WHOSE idea the Ping attribute was, or offer a compelling reason for its inclusion, particularly as it is something you can already do with onclick, as I mentioned here

    The "ping" attribute was proposed by Ian Hickson on 21 October of last year, as a quick search in the WHAT-WG mailing-list archive would have shown if you'd bothered.

    In his posting, Ian explaings the reasoning behind the attribute. You can do it with onclick, but then again you could manually write out every page of a dynamic website instead of using a CMS to automate the process.

  47. Re:Looking forward to it by RandomPrecision · · Score: 1

    There are several extensions for gestures in Firefox. These aren't extra programs that have to run in the background. For what it's worth, extensions are primarily why I haven't looked back at closed-source browsing.

  48. The Burning Edge by starbirdman · · Score: 2, Informative

    The Burning Edge, one of Jesse Ruderman's pages, is a pretty good resource to get a summary of what is the latest and greatest in Firefox development.

    He also has one that summurizes the differences between releases: http://www.squarefree.com/burningedge/releases/. It looks like he hasn't updated it for 2.0 yet though.

  49. Not much to see there. . . by kimvette · · Score: 2, Interesting

    Based on the screenshots, there isn't much new. While they readily admit the GUI isn't in place, I'd expect even an alpha build to reveal more of the functionality (otherwise it isn't alpha yet).

    One thing in the GUI that really catches my eye is the History menu, and the search option in particular. While you can search History via the sidebar in FF 1.5, it's somewhat weak. I'd guess that if they devoted a menu to History, they've vastly improved it. :)

    One thing I would LOVE to see is all of Tab Mix Plus to make it into the core functionality of Firefox. Actually there is a number of things Firefox (core application) sorely needs, natively out of the box:

      - a resizable search box (whose bright idea was it to make it a fixed width anyhow? Why should I have to download the Resize Search Box extension for such a basic thing?)
      - Session management - Opera does this out of the box, and I really like the session management extensions.
      - User agent switcher: Opera and Konqueror both do this natively. Firefox should as well, so that we can use coded-for-ie-and-only-ie web sites - again, without having to download and install an extension
      - Tab Mix Plus (mentioned above) - every other tabbed browser does natively what Tab Mix Plus adds. Firefox should do everything this extension provides, natively. Also, I should be able to "detach" a tab - this has really grown on me in Konqueror.

    --
    The Christian Right is Neither (Christian nor right). See: Matthew 23, Matthew 25, Ezekiel 16:48-50
  50. Re:Looking forward to it by DrSkwid · · Score: 1

    thanks for that

    The guy seems fairly sane.

    Though, personally, I think Eugenics is intellectual elitism gone up its own arse.

    --
    There are places where the networks are not touching,and there are places where they are-Boeing's Lori Gunter
  51. Mozilla browsers are filled with BLOAT by Anonymous Coward · · Score: 0

    it all went down hill when NCSA mosaic put a BLOATED and SLOW browser into the hands of the STUPID PROLES.

    As a member of the internet elite I DEMAND that we turn back the clock and take _OUR_ INTERNET out of the hands of the Walmart crowd.

  52. Bad idea. by SanityInAnarchy · · Score: 1

    Sometimes, I like to be able to close a pile of tabs at once. That's where keeping it in the same place is nice.

    But, there are already extensions that do what they're planning, so if you really want to break your tabbed browsing, you can do it on your own.

    --
    Don't thank God, thank a doctor!
  53. Alternatives to Opera by CarpetShark · · Score: 1
    1. Re:Alternatives to Opera by Anonymous Coward · · Score: 0

      How can you forget the classic Lynx? Or it's far superior updated version, Links? Links even has a gui version for you weirdos who must have pretty pictures. ASCII goodness is all I need, but some people apparently aren't satisfied with ASCII pr0n.

  54. In IE, it's all automatic by CarpetShark · · Score: 1
    IE7 Beta 2 solves this by showing the close button in the tab

    Don't worry, in IE, the website will close and open windows for you. You don't even have to think about it long enough to consent.
    1. Re:In IE, it's all automatic by rbarreira · · Score: 1

      Not with the popup blocker ;)

      --

      The AACS key is NOT 0xF606EEFD628B1CA427BEA93A9CA9773F
    2. Re:In IE, it's all automatic by CarpetShark · · Score: 1

      Yep, with the popup blocker too. Konqueror is the only browser I know that has a fully reliable popup-blocker. I certainly wouldn't trust IE's to work, given that Firefox's doesn't, and IE has been statistically shown to be much less secure. Time will tell, but until then, I'm assuming the worst, with good reason.

  55. Re:Redundant by Anonymous Coward · · Score: 0

    Given that Opera on KDE has a "Windows Native" theme that looks ugly as sin, I'd say popularity _does_ imply quality.

  56. I don't need this by Anonymous Coward · · Score: 0

    Brother you got that right.
    Extensions are the nuber one reason I linger at upgrading Firefox.
    What a freaking pain in the ass. (You could edit the exten. You could get a develeopment tool that turns off the version check.) You know, you could build an F'ing exention model that isn't a pain in the ass.
    How about a dialog box that says: "Your extension isn't made for this version. Do you want me to try to run it anyhow?"

    I also love searching for a new extension and being blocked from veiwing its webpage (at the Extension Bank) because my version number is incompatible. Then I have to play guess the complatible version number. It is one thing to watn me about downloading incompatible extensions. It is another to prevent me from even learning about them.

    Jesus Christ on a pogostick!

  57. Already done by njchick · · Score: 1
  58. Acid2 test? by onwardknave · · Score: 1

    Any news on how much, if any, the news of Opera's latest success passing the Acid2 Test will affect the development of Firefox? For Mozilla to stay ahead of the game, it needs to continue to do more than just staying ahead of IE.

    1. Re:Acid2 test? by mlefevre · · Score: 1

      None. Passing the Acid2 test needs some major reworking of things, which is going to take some time.

      The fact that Mozilla was "ahead of the game" with some other stuff gave Safari/Opera a headstart on Acid2. There aren't the resources to be ahead of everyone on everything all the time...

  59. I wonder if it'll be closer to passing ACID2? by mmell · · Score: 1

    No biggie, as this isn't even pre-release software; it seems to be more like a CVS/nightly to me. Still, it'd be nice to know that the Mozilla foundation are working towards that greatly to be desired goal.

  60. looks like 1.5 by LinuxRulz · · Score: 1

    Is it only me or do the screenshots look like FF 1.5. I don't see any differences between what I'm currently using. I think the article should be renamed:
    Mozilla Firefox 1.5 Alpha peeking out

  61. Tell Me More of your Developer Tools, Usul by WillAffleckUW · · Score: 1

    and we will share the fire of the fox.

    Seriously, can anyone give us a brief overview of what they are and why we should be really excited about the new Firefox Developer Tools option that I saw in the screenshots of the installation?

    Are we talking HTML, CSS, what?

    --
    -- Tigger warning: This post may contain tiggers! --
  62. I notice it imports settings/bookmarks from IE by WillAffleckUW · · Score: 1

    but not from Opera.

    Why?

    --
    -- Tigger warning: This post may contain tiggers! --
    1. Re:I notice it imports settings/bookmarks from IE by luserSPAZ · · Score: 1

      There certainly is code in there to migrate profiles from Opera. If you tried it and it did not work, you may want to see if there is a bug on file for that issue, and if not, file a new bug.

    2. Re:I notice it imports settings/bookmarks from IE by WillAffleckUW · · Score: 1

      thanks, what I meant was the screen shots said "Import IE profiles and bookmarks", not "Import IE and other profiles and bookmarks", so it's good to hear it will also import Opera.

      --
      -- Tigger warning: This post may contain tiggers! --
  63. Codecs are patented and trade-secreted by tepples · · Score: 1

    Is Quicktime a closed specification?

    QuickTime-the-wrapper is not closed, but QuickTime-the-included-codecs are. Parts of the Sorenson Video codec are patented; the rest is trade-secreted. The same goes for Apple's implementation of MPEG-4 video.

  64. Re:Redundant by WIAKywbfatw · · Score: 1

    So you judge a browser's worth by the native skin? Talk about judging a book by its cover.

    More worryingly, if you're saying that popularity implies quality (and, let's face it, you are) then doesn't imply that Internet Explorer is the world's best browser?

    QED.

    --

    "Accept that some days you are the pigeon, and some days you are the statue." - David Brent, Wernham Hogg
  65. Branch numbers are becoming very confusing by ishmalius · · Score: 1
    If you look at the trunk directory, you see that the packages are still numbered as 1.6a1 even though the dragbar says Alpha 2. Even more confusing, the build id in the About dialog says: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060318 Firefox/1.6a1.

    I get the impression that there are several main development branches running, not just the usual current branch/last branch/trunk trio.

    1. Re:Branch numbers are becoming very confusing by Anonymous Coward · · Score: 0

      There are three branches:

      1.0.1 branch - for Firefox 1.0.x security updates (1.0.8 is coming soon)
      1.8.0 branch - for Firefox 1.5.0.x security updates (1.5.0.2 is coming soon)
      1.8 branch - for Firefox 2.0 alpha 1

      and the trunk is for Firefox 3.0 (even though it's currently branded as "1.6a1")

      Some other things that need to be made clear:

      REMEMBER! "Nightlies" are not releases, and tinderbox builds are worse than nightlies.

  66. The EULA is idiotic by arrianus · · Score: 1

    Having an EULA pop up during the first run is idiotic for a free software project. There is no reason why the user must accept a license to run this program. EULA acceptance screens are needed for programs that add restrictions beyond regular copyright law (e.g. no reverse engineering). For programs with a free software license, which add additional rights (e.g. modify, but only if you distribute source to changes), it is not. The user either accepts or does not. If she does not, she has the rights granted by plain old copyright law, which means she can run it, but no copies or modifications. If she does, she has the additional rights under the EULA. The GPL has a nice clause and explanation about this.

    As is, this is nust an unneccessary additional user hassle. Why do we copy stupid things from commercial software when it doesn't apply? If the trend continues, by FX3, we'll have to type in a 20 digit product code to make sure it's a valid copy...

  67. The Official News Release from Mozilla News by Zitchas · · Score: 1

    In view of the following news released on the developers site, I think we can all take a deep breath and recognize that this was entirely overblown, and probably didn't really deserve to be mentioned on slashdot at all. Yet, anyway. If it actually was the newsworthy event originally claimed, then yes, deffinitly, but it's just alpha1, and not even a complete one, from the sounds of it.
    Taken directly from mozillanews

    BEGIN QUOTE HERE

    Code Freeze for 2.0 Alpha1 this Thursday at 11:59PM PST

    As discussed at the BonEcho status meeting today we will be doing a 1.8 branch code freeze on Thursday March 16, 2006 at 11:59PM PST in preparation for a Alpha 1 release next Tuesday.

    If you are trying to get a bug landed for Alpha1 please be sure to set the target milestone as follows:

    Firefox product: Firefox 2 alpha1
    Toolkit/Core products: mozilla1.8.1alpha1

    Ben G and Schrep will organize a quick triage session to stay on top of these bugs Weds/Thurs.

    The Alpha1 is primarily designed to test the places backend. The UI is not anywhere near final and mind the standard disclaimers about how it's alpha software and is thus buggy - so use at your own risk.

    END QUOTE HERE

    --
    Z
    1. Re:The Official News Release from Mozilla News by Anonymous Coward · · Score: 0

      I for one welcome our new Alpha release mozilla 1.8.1alph1 overlords!

    2. Re:The Official News Release from Mozilla News by chawly · · Score: 1

      Me too !!!

      --
      How many beans make five, anyhow ? ... Charles Walmsley
  68. looks like 1.5, but really 1.8.1 by WillAffleckUW · · Score: 1

    actually, it's mozilla 1.8.1 if you want to be technical ... which will become 2.0 alpha eventually

    --
    -- Tigger warning: This post may contain tiggers! --
  69. Re: "try to run it anyhow?", plus general comments by rickst29 · · Score: 1
    First of all, Mozilla.org has CUT THE BRANCH Alpha-1, but the test builds are not yet good enough to designate the result as the 'Alpha1' RELEASE.

    The extension "Nightly Tester Tools" allows you to ignore the build IDs in the .xpi file, 'forcing' compatibility. They'll at least load once... they might, in some circumstances, immediately disable themselves. Or, they might break completely.

    When it happens, the 'Alpha' designation means that no more major new features will be allowed from that point onwards. Also, it should be at least somewhat useable. It DEFINITELY doesn't mean that it's ready 'informal' use... you need to make a COMPLETE backup of your profile before installing one of these nightly builds.

    The biggest new feature is 'places', a gigantic re-write of 'bookmarks' to include RSS and some new features. IMHO, it's badly broken. I've used several nightlys in recent weeks, and disasterous problems, (already known, but still to be fixed) have forced me back to a mid-February build.

    Be sure to check the mozillazine forum firefox-builds (at http://forums.mozillazine.org/viewforum.php?f=23 , NOT the firefox-support forum) for the most recent "The Official Win32 2006mmdd Build is out" thread. Then, look at the unfixed bugs in the list. And ***IMPORTANT*** use the last link in the bugs list to look at the separate list for 'places'.

    As I write this, the Places list includes 216 bugs. One is a 'BLOCKER', another is 'CRITICAL' , and 15 are 'MAJOR'. I wouldn't use the current nightly on my box. (With my usage, the 'Critical' is more important than the 'blocker'). But, in any case, I'd recommend that you wait until there aren't any 'CRITICAL' bugs which could affect you before downloading any nightly.

    *IF* you download and use a nightly, I say that you are MORALLY OBLIGATED to check for duplicates on any bugs you find. Right now, that means you've got 194 'normal', 'blocker', and 'critical' bugs to cehck against... just for places.

    for everyone's sake, WAIT FOR A HALF-DECENT BUILD!

  70. download the portable 2.0 alpha instead.. by atarione · · Score: 1

    http://www.cybernetnews.com/?p=411

    since the alpha appears to have unistall "Issues" i would strongly suggest using the portable build if you wanna try it out.

    --
    actually I am happy to see you, however that is in fact a banana in my pocket.