Slashdot Mirror
Mozilla 1.8 Alpha Released
AllMightyPaul writes "Last Friday, the Mozilla Organization announced Mozilla 1.8a. You can download Mozilla 1.8 alpha (with torrents available) from the Mozilla public FTP server. Features include a basic upload FTP UI, improved junk mail filtering, and the number of cookies that Mozilla can hold has also increased 'dramatically.' What's amazing is that they haven't even released Mozilla 1.7 yet. Here I thought that Mozilla was going to standardize on 1.7."
But despite standardising 1.7, development of mozilla continues.M E.html for details.
1.7 is about third party developers and products which rely on a fixed api.
1.8 is where new features will be found.
New features are for example ftp upload capability, use of 4. and 5. mouse button.
see http://www.mozilla.org/releases/mozilla1.8a1/READ
But this news is already 8 days old. I wonder why this is picked up only now.
improved junk mail filtering
I really don't understand why this is still a live issue. When I used to use Outlook I used SpamBayes to filter my spam and within a few days it was catching 99.99% of my spam. That's obviously a made-up figure, but that's how it felt. I never missed a single real mail, and after a few weeks I don't think a single spam ended up in my inbox.
Then I moved to Thunderbird, and suddenly obvious spam is regularly ending up in my inbox, despite several weeks' training. Don't get me wrong, it's a great mail client, but I don't see why it's so hard to implement something that's already been done perfectly in more than one open-source project?
For their poor servers ...
Win32 exe
Win32 Zip
Linux
Linux (installer)
You can configure Mozilla to play nice with Outlook, check out the cool tip:
h tm l#other-default
http://www.mozilla.org/start/1.4/faq/mail-news.
It always works for me, too, in both Firefox and Bloatzilla. In fact, unlike Opera, there doesn't seem to be a way to make a middle button click on a link do anything else, from the Options menu (Preferences in Opera).
Mod parent up!
I was thinking exactly the same thing. Makes a nice punchline: "The 1990s called. They want their fonts back." :-) Joking aside, I think it is indeed a regression. The Burning Edge
Firefox nightly build blog says that gtk2 builds don't start (since May 11). It could be an unrelated firefox-specific problem, but I'm guessing there's a connection.
Never. It was the initial plan to rename it to Mozilla Browser, but now they have settled on Mozilla Firefox as the permanent name (it no longer remains simply the codename).
hey look features are features but a few are missing
I would like a IM client (IRC does not rock my world) a Jabber client would be good
jabber support
I would like a iCal clone... (in process)
Indeed it is :)
I would like OpenPGP intergrated (only 128bit to save the export legal stuff) just basic crypto would be great (make it easy to setup as well)
There's a gpg extension, will that do?
I thought Firefox was scheduled to be *the* browser in the suite [...] How does that work if Firefox is on a branch and the suite ploughs ahead?
Firefox is only on a branch for 0.9 and 1.0. That's no different from how Mozilla 1.7 is on a branch. Future versions of Firefox will be built from the trunk (or, more likely, from a more recent branch from the trunk), and thus will contain all the backend work that's been going on since 1.7 branched.
Of course, you're welcome to download the trunk builds of Firefox (which are being made available daily) -- you'll get the same backend fixes that 1.8 Alpha1 has, but it won't be anywhere near as stable as the branch builds.
I hope bugfixes [...] are consistantly and promptly backported to 1.7 (and thus to Firefox)
Actually Firefox is on its own branch now, based off the 1.7 branch. And no, not all fixes will be backported, that's the whole point of having a branch. And the bug you mentioned isn't even fixed yet.
or the impetus could be there to reverse the flow back to the suite
That doesn't make sense. If you wanted the bug fixes that 1.8 had, you could just get a 1.8 build of Firefox instead of the one from Firefox' 1.0 branch. No reason to switch back to the suite.
You know, Microsoft's street address also says a lot about their mentality.
You get everything or nothing: I can't decide just to have the web browser and html editor: but I'd rather use my existing email app so I don't want that taking up resources on my machine.
Yes you can - you just select "Browser" during the install process and deselect the other components. It's really not that challenging.
Ok, im no 'zilla expert here, but ever since I can remember Mozilla (or at least Firefox) has supported opening tabs on middle click.
Well, you're mostly right. Tabs were added prior to the 1.0 release, and middle-click to open the tabs was turned on then...except on OS X.
Kindly see Bug 151249 -- Middle click on links does nothing in OS X (You'll have to copy that link, bugzilla has a referrer check to block links from slashdot.)
Unfortunately, Carbon doesn't have the ability to recognize a middle mouse click, so Mozilla (Seamonkey) and Firefox can't do anything on a middle click. Camino, on the other hand, is built with Cocoa, so middle-clicking works on a default build.
Combine this with the lack of Ctrl+Enter URL autocomplete, and I don't enjoy my Mozilla experience on OS X. I use Firefox on a daily basis on both Windows & Linux; the second I go over to my Powerbook, Firefox doesn't behave even close to the same way, and it drives me crazy. I still use it, because I really dislike Safari's interface, and it's still missing too many features, but Mozilla on OS X needs a chunk of work before it will act like it does on other OSes.
They didn't add an "FTP client" - they added UI to allow FTP upload. The FTP back-end is useful for other stuff, and was already present - adding the menu command wasn't a huge thing.
Why? Who decided that? Why can't obvious UI mistakes be fixed?
:-)
Not everyone has the same definition of "obvious UI mistake". Same point as last time.
nobody has the balls to draw the plans for Mozilla 2.0.
Says who? Just because we haven't reached the stage where it's appropriate to publish them doesn't mean they aren't being looked at.
That's all it takes to spin a 2.0, nothing more.
You've got it all backwards. You don't pick a version number first and a set of features second. We are not thinking "goodness me, what can we do so that it looks sensible calling it 2.0?", we are thinking "what's the next big step in Mozilla's evolution?" and, incidentally, deciding to call it Mozilla 2.0.
it also gets Mozilla a new fresh round of much needed media coverage.
Who says the Mozilla suite needs media coverage? It's certainly not obviously true. One could argue that we should spend all our effort getting media coverage for Firefox and Thunderbird.
Also, there is no plan to leave maintenance mode at the moment
No, and that's the point. That's what maintenance mode is. Seamonkey is still around because some people care about it, but they care about it being like it is now. Any massive marketshare increase we get will be driven by Firefox, not by Seamonkey.
Heck, you could hold "Vote for Mozilla 1.X splash screen" sessions at Mozillazine.
A vote is (well, was originally, it's now mostly inertia) the reason the suite is stuck with that current weird throbber. Votes, in general, suck as a way of choosing anything. Open Source projects are (mostly) not democracies.
If you want to be listened to, come out from behind that cowardly anonymity and engage in constructive discussion.
Gerv