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.
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.
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.
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.
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.