Slashdot Mirror

← Back to Stories (view on slashdot.org)

Mozilla 1.4b Loosed

Posted by timothy on from the lizardly-goodness dept.

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

11 of 354 comments (clear)

  1. Also, 1.3.1 by friedegg · · Score: 5, Informative

    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.
  2. New Phoenix/Firebird builds too by Patik · · Score: 5, Informative
    It's been updated a lot since the 0.5 milestone, I suggest you check it out. There are several new features and UI enhancements.

    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.

    1. Re:New Phoenix/Firebird builds too by pipegeek · · Score: 5, Informative

      Is Phoenix the same thing as Firebird?
      Yes. They renamed Phoenix to Firebird due to some trademark dispute.

      What about Thunderbird?
      Thunderbird is a new email client which is (I believe) being written to accompany Firebird.

      What's the difference between them and SeaMonkey?
      Seamonkey is what Joe User would know as "mozilla". It's (I believe) the codename of the current mozilla app suite, which is based on XPFE. These new projects (Firebird and Thunderbird) are designed using new, faster toolkits (and are themselves much smaller and more streamlined) but they still make use of Mozilla's gecko rendering engine. These two projects are slated to replace seamonkey in mozilla 1.5 and all subsequent releases. They are, however, currently available as standalone programs (though, from what I've heard, Thunderbird is still a bit not quite there).

    2. Re:New Phoenix/Firebird builds too by fishbert42 · · Score: 5, Informative
      You should check out the new Mozilla branding strategy. It should answer your questions. In particular:

      Before defining how we talk about something and how we want to present it to the world, we should talk about what we're actually producing. Right now we have two basic projects:
        1. SeaMonkey: The SeaMonkey project is also called the Application Suite or "App Suite." It's largely the same as the old Netscape 4.x Communicator brand. It has more or less the same functionality and branding as that the old 4.x product and we've done little to counter that association.
        2. Firebird/Thunderbird: These are the basis for the second generation mozilla products. They split our application into two separate applications with separate identities: a web browser and an email program. In talking about these projects, we should allow them to have their own identities.
  3. Loosed? by Anonymous Coward · · Score: 5, Funny

    Mozilla 1.4b Loosed

    Good lord, when you people learn, it's LOSE, not LOOSE! LOOSE means to "let loose, to free, to release", and LOSE mea...

    Erm.

    Never mind. You got it right this time. Carry on then.

  4. Re:support for NTLM authentication by Lieutenant_Dan · · Score: 5, Insightful

    Actually, that could be a good thing. It may lead to a deployment of Mozilla within an organization that has resources secured by MS server packages (IIS, SQL Server, etc).

    In my opinion this shows the Mozilla team being a bit more agressive in making inroads into the corporate (sometimes MS-dominated) world. Good for them.

    --
    Wearing pants should always be optional.
  5. Re:I used to follow mozilla by GuNgA-DiN · · Score: 5, Informative

    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.

  6. image blocking by rock_climbing_guy · · Score: 5, Interesting
    Image blocking/disabling is now more flexible and users can "view image" to see blocked or not loaded images.

    I have an idea for image blocking. Now that Mozilla uses a statistical technique to identify spam, presumable with some sort of set of words to begin the database before it is trained with our spam messages, perhaps we could apply some sort of guessing technique for image blocking.

    A central database of crap ( read Doubleclick.net ) images could be maintained. Images could be checked against the database and then blocked or allowed based on that. Perhaps the domain that the images come from could be taken into account as well.

    --
    Wh47 d1d j00 541, 31337 15n't t3h r0xor5 ne m0r3???
  7. NTLM is good for some people by koh · · Score: 5, Insightful

    Many people will consider NTLM support as superfluous pro-MS bloatware and another useless addition to Mozilla.

    I'd like to point out this is just plain wrong. There are many developers that are forced to use IE to do their job just because the company's product runs on IIS and uses NTLM.

    Mozilla supporting NTLM means better ways of testing software for these developers, as well as giving a better idea of the web homogeneity of the product.

    Free myself from IE at work ! Go for NTLM, Mozilla ! :)

    --
    Karma cannot be described by words alone.
  8. Re:NTLM for Linux? by mr_goodwin · · Score: 5, Informative

    Check out the NTLM authorization proxy server here.


    That's what I use.

  9. Re:SVG Support by Anonymous Coward · · Score: 5, Informative

    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.