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.
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?
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
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.
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 :-)
Animoog.org
Karma whore +99999
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.
.. 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.
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.
The idea of people who actually write markup language specifications and know a heck of a lot more about the internet than you do.
See also A blog post by someone who actually makes browsers and also knows a heck of a lot more about the internet than you do.
There are 11 types of people in the world: those who can count in binary, and those who can't.
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.
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.
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
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.