Slashdot Mirror
Mozilla 1.4b Loosed
An anonymous reader writes "The fine Mozilla folks have decided to bless us with the release of Mozilla 1.4b this weekend. Highlights include support for NTLM authentication, usability improvements, and lots of performance, stability, and site compatibility fixes. As always, the release notes have more detailed info on changes."
Mozilla 1.3.1 (bugfix update for 1.3) was released this week, too.
Google doesn't index user sigs, so stop trying to "Google Bomb" with them.
ftp://ftp.mozilla.org/pub/phoenix/nightly/latest-t runk
Also check out all of the extensions, most of which still work on the latest nightly build.
Mozilla 1.4a is "alpha" (hence the "a"). Likewise, Mozilla 1.4b, the version being mentioned in this article, is "beta" (hence the "b"). Once Mozilla 1.4 is finished, it will be released as simply "Mozilla 1.4" and that'll mean it's stable.
Then a few months later some minor bugs will be ironed out (or in a few minutes some major bug will be) and that'll be Mozilla 1.4.1. By that time, Mozilla 1.5 may very well be starting its own release cycle.
Definitely! I love tabbed browsing, and the popup and cookie features are far superior to IE. Mozilla has become my primary browser. I've been investigating the calendar feature too. I plan on proposing that we implement it company-wide at my work. Mozilla has matured greatly and it's only getting better. You should check it out again.
Check out the NTLM authorization proxy server here.
That's what I use.
Is this what you're looking for?
Shameless plug: if you run Squid, here's mine.
$x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
$x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
I wish they could make Mozilla a little faster and lighter, than add features to it.
They're working on this. Mozilla is currently one big app that does everything (browser, mail and news client, HTML editor, IRC client, etc. etc.). It's being split into 1) the Gecko rendering engine, 2) a browser code-named Firebird, 3) a mail client code-named Thunderbird, etc. Each application will be able to be installed separately. Once this is done, it should be easier to optimize each component for speed.
$x='S24;r)>63/* h@<5+oZ)32"5cz';$me='phroggy'x$];
$x=~y+ -xz+\0-Tx+;print$_^chop$me for split'',$x;
No, firebird will package with minotaur to provide e-mail.
Look at the roadmap for more information.
Ryan
Add a link to firebird in your start-up folder, with "-turbo". It will then rest in your toolbar. When you go to launce firebird for real, the window will come up much quicker.
Ryan
No, domain\username only worked for standard 'clear text' http authentication, which on IIS servers maps domain usernames like that. Actual NTLM authentication is a different protocol altogether. If a server enabled NTLM authentication but not clear-text, you were out of luck. Also, I believe that NTLM allows for transparent authentication, where your current user/domain login to Windows is used (without having to type anything), though that may just be an implementation detail of IE.
Thanks, Mozilla installer team! You have successfully produced an installer that prevents me from ircing while Mozilla installs!
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
SVG support is still very much incomplete; the browser won't recognise SVG that is embedded into pages using the embed tag (which is pretty much all SVG on the net, since that's what the Adobe plugin supports best). It also doesn't have support for the entire spec, although for basic static graphics, it is pretty much there. The libart licensing issue to which you allude is a simple incompatibility between the MPL/LGPL/GPL trilicense that Mozilla is released under and the LGPL of the libart library. That pretty much prevents mozilla including SVG by default at the moment. In addition, a lot of the SVG had a rewrite quite recently and, because no one has had time to review thousands of lines of new code, it's still living on a branch. That's important if you decide to compile Mozilla with --enable-svg set - to get the new code you need to pull the branch from CVS, otherwise you'll get the older, somewhat buggier code. For more details, including quite detailed build instructions, see http://www.mozilla.org/projects/svg/ If you think that duplicating cpu effort by compiling everything yourself is a waste of time, then there are regular svg-enabled builds contributed to ftp://ftp.mozilla.org/pub/mozilla/nightly/latest These come in two flavors, GDI+ (windows only) and Libart (Linux and windows). All svg builds have mathml-svg in the filename. If you're not on one of those platforms or want something cool like Xft and SVG, you'll need to complie yourself, I'm afraid. For more information, see the netscape.public.mozilla.svg newsgroup.
Comment removed based on user account deletion
Mozilla 1.4 beta includes a security fix to prevent web pages from loading XBL from file: URLs (bug 200691, fixed). Unfortunately, the fix also prevents user style sheets from making web pages load XBL files from file: URLs (bug 204140), which affects some users of my XBL Flash blocker (blocks Flash using a placeholder that you can click to play a particular Flash animation).
If you saved flash.xml to disk and used a file: URL for flash.xml in userContent.css, you need to change userContent.css to load flash.xml from a local web server or from the original location on www.cs.hmc.edu instead. Otherwise, Flash won't appear at all (not even a click-to-play placeholder), and you'll see this if you open the JavaScript Console:
"Security Error: Content at http://www.shockwave.com/sw/home/ [or another URL with Flash] may not load or link to file:///C:/.../flash.xml#obj."
The shareholder is always right.
You can see the about:* pages for MSIE and edit them in the registry at Hkey_Local_Machine/Software/Microsoft/Internet Explorer/AboutURLs.
Joe Llywelyn Griffith Blakesley
[This post is in the public domain (copyright-free) unless otherwise stated]
> Standard HTTP authentication is hideously broken. It's plain text. Period. That's all there is to it. It's goddamn plain text.
Bogus. See RFC 2617 section #3, which outlines Digest (MD5) authentication. Digest auth is far superior to NTLM auth because it uses stronger crypto. The only reason to support NTLM is for compatibility with older microsoft products.
Darin