Slashdot Mirror


Mozilla 1.6 Beta Released

Sick Boy writes "As reported on Mozillazine, the Mozilla Foundation today released Mozilla 1.6 Beta. This latest milestone adds support for NTLM authentication on all platforms and improves the implementation on Windows. The automatic page translation feature has been restored (now powered by Google Language Tools) and a new version of ChatZilla, 0.9.48, is now included. In addition, several security and crash bugs have been fixed during the beta release cycle. Builds can be downloaded from the Mozilla Releases page or directly from the mozilla1.6b directory on ftp.mozilla.org. The Mozilla 1.6 Beta Release Notes have more detailed information about what's new and known issues to watch out for."

108 of 404 comments (clear)

  1. Torrents by shamilton · · Score: 5, Informative
    --
    "[A] high IQ is like a Jeep; you will still get stuck, just farther from help!" --Just d' FAQs, c.g.a
    1. Re:Torrents by Aaron+England · · Score: 3, Insightful

      And why should we trust you to provide tampered-free code?

    2. Re:Torrents by shamilton · · Score: 5, Informative

      You shouldn't. Good thing they provide MD5 sums.

      --
      "[A] high IQ is like a Jeep; you will still get stuck, just farther from help!" --Just d' FAQs, c.g.a
    3. Re:Torrents by t0qer · · Score: 4, Funny

      Not that I doubt they can take the load, but why make 'em?

      Holy Smokes! 1 peer, 1 seed and 184kbps??

      You sir are seeding from the bandwidth of the gods!! My hats off to you!

    4. Re:Torrents by SpaceRook · · Score: 2, Informative

      OK, it works like this: you go to the Mozilla site and download the source code. Then you add your own malicious code into the source. Then you host the source on your own site claiming to be a legimate mirror. A knowledgable user would download your source code / binaries and compare the checksum to the checksum of the real code. If you altered any code, they will not match.

    5. Re:Torrents by pi+radians · · Score: 4, Funny

      I download stuff at 2 Megabytes per second usually. I get my linux isos in 350 seconds.

      Wow. I bet that gets the ladies all wet and anxious. You must be swatting them away like flies with bandwidth like that.

      --

      sin(6cos(r)+5A)
    6. Re:Torrents by 4of12 · · Score: 2, Insightful

      knowledgable user would download your source code / binaries and compare the checksum to the checksum of the real code

      Note the parent poster provided links to mozilla's main site for the md5 checksums.

      If he were distributing corrupt binaries he would have to either:

      1. get binaries' checksums to match the old binaries' checksums (nigh on impossible, given how md5 hash works), or
      2. replace the md5 sums on mozilla's main site (and the binaries, for consistency), or
      3. hijack routers or DNS so "mozilla.org" isn't right.
      You're right, though, to be developing a healthy paranoia....
      --
      "Provided by the management for your protection."
  2. very nice by koekepeer · · Score: 4, Insightful

    especially things like the NTLM authentication support on all platforms gives us a stick to beat the anti-opensource FUD spreaders with

    see? it works!

  3. I'm confused... by Fnkmaster · · Score: 4, Interesting
    The roadmap has implied for some time that 1.4 was the last unified (XPFE) Mozilla-based release. 1.5-1.6 was supposed to be the Firebird transition period, during which Mozilla-the-unified-browser was supplanted by Thunderbird and Firebird. Perhaps that was too ambitious, and they've changed their mind, but the roadmap (here)still indicates otherwise.


    What's the deal? It really looks like the new roadmap is "build in all the features people REALLY bitch about into XPFE Mozilla, then once Firebird/Thunderbird is more stable, we'll transition to those". I'm fine with that, but shouldn't they just come out and say it?

    1. Re:I'm confused... by Dickolas+Wang · · Score: 2, Interesting

      If I recall correctly, there was a really tiny note at the bottom of the roadmap or of the 1.4 release that said that it was not going to be possible anymore. Speculation was they were hit really hard by the demise of Netscape (and thus the loss of umpteen Gecko developers). I think this more than anything put off Firebird being anointed the new Mozilla Browser.

    2. Re:I'm confused... by superyooser · · Score: 4, Informative
      Go here and scroll down to the post by jasonb (a moderator).

      Elsewhere on MozillaZine, somebody (sounding authoritative) said that the transition would occur in the first half of 2004. Nobody really knows. I would guess that it will be at least two more versions after 1.6, but I am not a Mozilla developer.

  4. SVG support by AllergicToMilk · · Score: 4, Interesting

    Ah, but when will they add SVG support to the standard build. I suspect we will always be tied to the non-open Flash format until someone steps up and makes SVG support in a browser standard.

    --
    There are only 6,863,795,529 types of people in the world.
    1. Re:SVG support by gngulrajani · · Score: 2, Insightful

      looks like adobe has not updated there client to support the 'stable' version of mozilla

      http://plugindoc.mozdev.org/linux.html

    2. Re:SVG support by gaspyy · · Score: 5, Informative

      the "non-open Flash format" argument is so old is not funny anymore.

      The Flash IDE is proprietary. The Flash file format is open and documented. You can write your own program to create or read flash files like so many have.

      SVG may be nice but with 98% market penetration I don't see Flash disappearing anytime soon. Also, considering its graphics+animation+sound+video (sorenson based) capabilities, coupled with a pretty good language (based on ECMAScript 4), Flash is a very powerful tool.

      I realize that /. is an anti-Flash crowd, but as a technology Flash is no more evil than animated gifs. Both are abused by advertisers but both have legitimate uses.

  5. Re:Mozilla is a great browser by Anonymous Coward · · Score: 3, Funny

    Yeah, u get free Internet Explorer on Windows so why not use it then, what will u lose anyway

  6. Any news on AmiZilla? by Amiga+Lover · · Score: 3, Interesting

    Any news on how the port of mozilla to AmigaOS is going?

    1. Re:Any news on AmiZilla? by mios · · Score: 3, Funny

      I think the development team dropped that in favor of the ComiZilla project ... the port of Moz to the Commodore 64 ( ... the lead developer's email is apparently mccarthy@mozilla.org).

    2. Re:Any news on AmiZilla? by Anonymous Coward · · Score: 4, Informative

      Dead as a doornail. IIRC it began around the time of Milestone 9 or something, and nothing was ever released in public.

      Besides, why do you ask on Slashdot?
      Try a more specific site like ANN.lu or amiga.org.

      (Or if you want to be fed with lies and hear everything's A-OK and you should send more money to "Amiga, Inc." in order to "support the community", then head over to AmigaIncOtherworldly.nuts)

  7. Firebird is WAY better than Mozilla by Anonymous Coward · · Score: 2, Interesting

    It's smaller, faster and supports the W3 far better than IE. It's also incredibly extensible - if you are a web designer you simply must try out the webtools bar. And I thought it was supposed to take Mozilla's place. Why haven't they killed off Mozilla yet?

  8. Legal Ramifications Resulting From Use of NTLM by use_compress · · Score: 5, Interesting

    From http://www.mozillazine.org/talkback.html?article=3 990
    Microsoft's NTLM authentication protocol, popular on Windows-based corporate networks, is now supported by Mozilla on all platforms. Previously, NTLM authentication was only available to Windows Mozilla users, requiring the presence of the Windows SSPI API. Now, the SSPI code has been discarded and a cross-platform implementation has been checked in.

    This makes me wonder if Microsoft will peruse legal action to block Mozilla from using a cross-platform, non MS implementation of an MS technology. Because NTLM is undocumented, I wonder what the legal ramifications of implementing it are? Do you own a copyright to an undocumented technology?

    1. Re:Legal Ramifications Resulting From Use of NTLM by jopet · · Score: 5, Insightful

      no - on what grounds should this be a problem? Copyright applies to original work - no original work of MS was copied or used for implementing this. Also, no secret documentation was used and no animals were harmed. I do not see a problem.

    2. Re:Legal Ramifications Resulting From Use of NTLM by srn_test · · Score: 4, Informative

      It's nothing to do with copyright.

      Since it's undocumented and the implementors have (presumably) never seen the MS code, there can be no copyright problems or IP leakage.

      The only problem may be if MS has a patent on something fundamental in the NTLM system...

    3. Re:Legal Ramifications Resulting From Use of NTLM by cgranade · · Score: 2, Insightful

      Just because it isn't a problem for us doesn't mean that the law agrees, er go DMCA.

      --

      #define DRM chmod 000

    4. Re:Legal Ramifications Resulting From Use of NTLM by YouAreCorrect · · Score: 3, Informative

      The DMCA does no apply to this. While it can be argued that this is reverse engineering an access control mechanism, that it is for interoperability, which is protected under the DMCA, cannot really be argued.

  9. because ... by jopet · · Score: 3, Insightful

    Because IE is insecure, does not have popup blocking, lacks many other features Mozilla does have and supports W3C standards better. Plus, it comes with a mail client that is more secure than outlook and has a well working spam filter built in.

    1. Re:because ... by Anonymous Coward · · Score: 5, Funny

      Because IE is insecure, does not have popup blocking, lacks many other features Mozilla does have and supports W3C standards better. Plus, it comes with a mail client that is more secure than outlook and has a well working spam filter built in.

      So apart from what's not in bold text above, you're saying that IE is a better browser?

      Work on that syntax, son. ;)

  10. Deja-vu by a.koepke · · Score: 3, Informative

    I was getting a bit of Deja-vu reading the NTLM stuff since I was sure they had announced it earlier.

    NTLM support on all platforms was announced on the 18th of Nov and has been available in CVS since then.

    --


    (\(\
    (^.^)
    (")")
    *This is the cute bunny virus, please copy this into your sig so it can spread
  11. Re:I don't understand by zspoelstra · · Score: 2, Informative

    there is no stable 1.6 release yet. The latest stable was 1.5.1 I believe

    Alpha-> Beta-> Final

  12. Re:I don't understand by AntiOrganic · · Score: 2, Insightful

    When you optimize code or add new features, you also introduce new bugs that weren't there before. Out with the old, in with the new.

    They obviously haven't spotted the new, so it's a beta.

  13. Beats me too... by Kjella · · Score: 3, Insightful

    ...I'd think that getting Firebird & Thunderbird going, which seems to be a lot more plug-in oriented would make it easier than the "One tool to please them all" that they're trying to make Mozilla into.

    Oh well, I won't complain, I'll just use Firebird in it's 0.x stage, it's more than stable enough for that anyway. Maybe they'll come in version 2.0 after all?

    Kjella

    --
    Live today, because you never know what tomorrow brings
    1. Re:Beats me too... by koekepeer · · Score: 4, Insightful

      i don't get you... how do you mean "one tool please them all that they are trying to make Mozilla into?"

      Mozilla *is* and *was* already a "swiss-knife" application. including a kitchensink ;)

      but yes, i agree completely that a more modular, plugin-style architecture would make things a lot better (more maintainable). just have a little patience... apparently it takes more time than planned

    2. Re:Beats me too... by chabotc · · Score: 4, Informative

      Unfortunatly the kitchensink patch isn't in the mainstream mozilla yet (see bugzilla.mozilla.org, bug 122411)

      However you can view it in all it's glory here: http://www.mozilla.org/docs/web-developer/samples/ kitchensink.xml

  14. Firebird merged, When ? by Anonymous Coward · · Score: 2, Interesting

    Sorry guys, but IMHO Firebird is what mozilla should habe been : nice look, 'speed-o-light' fast, IE killer ...

    And last time i used mozilla (a year ago), it was slow, ugly, and somehow much buggy !

    So my question is, when will they merge the two project ?

    1. Re:Firebird merged, When ? by a.koepke · · Score: 2, Informative

      I don't think they are merging it, they will keep working on the Mozilla core but not release any more Seamonkey (Mozilla Application Suite) milestones.

      --


      (\(\
      (^.^)
      (")")
      *This is the cute bunny virus, please copy this into your sig so it can spread
    2. Re:Firebird merged, When ? by Vlad_the_Inhaler · · Score: 2, Informative

      a year ago, mozilla was slow, ugly, and somehow much buggy. I use 1.5 and it is fine, so - on the whole - (there was a problem with font-sizes when printing) was 1.4.

      --
      Mielipiteet omiani - Opinions personal, facts suspect.
    3. Re:Firebird merged, When ? by JCholewa · · Score: 2, Informative

      > Sorry guys, but IMHO Firebird is what mozilla
      > should habe been : nice look, 'speed-o-light'
      > fast, IE killer ...

      Yeah, 'speed-o-light' ... maybe in an alternative universe where c 10m/s

      I have Firebird 0.7 installed here. To start it up (from an initial zero-window state) on this 550MHz Pentium III, I have to wait something like ten and a half seconds.

      Mozilla 1.5 has this nice feature that lets you preload the application. Because of this, I can start from the same zero-window state and get a new browser window open in two seconds.

      Until Firebird has this functionality, I can't use it.

      For that matter, while I use a modified Qute skin (that's what Firebird uses) for Opera, I vastly prefer using the Walnut skin for Mozilla, since it looks a ton better. I don't think that I can use this skin with Firebird. I will check, though.

      --
      -JC

  15. IP 101 by Kjella · · Score: 4, Insightful

    Do you own a copyright to an undocumented technology?

    No, you can't own a copyright on a technology - only on an implementation. You can however, own a patent on a technology. However, you can not patent an API, though you can patent an algorithm used by the Windows implementation of that API, in which case you'd have to find another way to implement it. However, since it's undocumented, there's also no known patents to avoid.

    Besides, it would probably fall under the legal protection of reverse engineering for interoperability anyway.

    Kjella

    --
    Live today, because you never know what tomorrow brings
  16. Ugh, stop wasting time with this already. by Visceral+Monkey · · Score: 2, Insightful

    Firebird is clearly the chosen one. I wish they would put a final stake through the heart of the old mozilla and pass the mantle to Firebird already.

    --
    *Fortitudo, aequitas, fidelitas.*
    1. Re:Ugh, stop wasting time with this already. by jopet · · Score: 4, Informative

      There are many users who prefer MozillaSuite for many good reasons (more features, several components nicely integrated, no need to download countless extensions, ...). Apart from that, FB/TB are still "technology previews" with many problems.

  17. I disagree by jopet · · Score: 5, Informative

    FB is hardly that much faster - it uses exactly the same rendering engine and set of libraries under the hood, so there is just a tiny speedup from the GUI that is unnoticable on modern fast computers. It does NOT support W3 better or worse, since it uses exactly the same Gecko engine. And it lacks many features of Mozilla that need to be brought back through extensions. And inflationary extensions can eventually cause severe security problems.

    1. Re:I disagree by ahriman · · Score: 2

      The post you replied to stated that Firebird "supports the W3 far better than IE" you misunderstood.

    2. Re:I disagree by hacker · · Score: 2, Interesting
      "It does NOT support W3 better or worse, since it uses exactly the same Gecko engine."

      Actually, the HTML rendering in 1.6 changed in very ugly (i.e. broken) ways. I can have 1.5 and 1.6 running against a site, such as our bugtracker for Plucker, and the way it renders the tabled HTML changes. colspan is broken and appears to be "reversed" (adding a colspan incrementor, shrinks the width of colums spanned).

      There are a few places where it completely ignores CSS values for coloring as well, leaving pages which contain a named class in one place colored, while that SAME CLASS in another place on the SAME PAGE is left white.

      So far, 1.5a is the best I've tried. Fast, lean, and properly handles validated HTML and CSS constructs.

  18. Skins by Kethinov · · Score: 3, Interesting

    Warning, this is semi offtopic.

    As much as I love Mozilla as a regular user both in Windows and in Linux (using it now) I really wish they would fix backwards compatability with older skins. There's some really nice KDE skins out there (one in particular on KDElook that I love) that I wish I could use.

    --
    You're right, I wouldn't steal a car. But if it were possible, I sure as hell would download one!
    1. Re:Skins by Kethinov · · Score: 2, Insightful

      Your point is well taken, but consider the fact that Mozilla is very much complete. It's got tabbed browsing, popup blocking, and a boatload of other little features. AND it doesn't crash like certain other browsers we're familiar with. What needs help now is the skinning system. The very least they could do is come up with a new skinning system that won't break backwards compatability every time a new version is released.

      --
      You're right, I wouldn't steal a car. But if it were possible, I sure as hell would download one!
    2. Re:Skins by cscx · · Score: 2, Interesting

      AND it doesn't crash like certain other browsers we're familiar with.

      You mean like, .... Mozilla?

      I've used IE for a very long time and it is WAAY more stable than Mozilla. In the short times I have used Moz, it has crashed way more times than IE has ever crashed on me. Ever. Mozilla 1.5 had this nasty habit of crashing on me EVERY TIME I exited the browser. I don't call that "stable." And NO, it wasn't the fault of any configuration or faulty hardware or any other stupid reason someone can come up with.

      BTW, i use Firebird now ;)

    3. Re:Skins by bgfay · · Score: 2, Informative

      Backward compatibilty with skins doesn't seem like the biggest issue to me. I worry that developers get too caught up in supporting what was and that limits what can be. Don't get me wrong, I'm not looking for open source developers to do a Word format thing where they keep changing the format to get everyone to upgrade, but neither do I want a system whereby every legacy app is supported in the new version and thus, everything is clunky.

      I'm not saying this as well as I had hoped. But what I guess I'm talking about is that I was very impressed when the Mozilla team made the decision to jettison the old Netscape code even though that meant a longer development cycle, backlash from lots of sources, and a host of other PR problems. By starting from scratch, they produced a product that is incredible, far better than if they had stayed with the old code.

      So, if a few skins don't work, for me, that's not a big deal.

      Then again, I'm just one user.

      --
      Yeah, I'm as old as my UID would suggest.
    4. Re:Skins by Anthracks · · Score: 2, Insightful

      That's much easier said than done unfortunately, if you look at why the skins break a lot of the time. Skins are basically just sets of style-sheets and images that are applied to the user-interface widgets (which are defined in XUL, the XML-based user-interface language Mozilla uses). If anything major changes in the XUL definitions, like a new UI element or a renamed UI element, or an element is moved around to a more appropriate place, the CSS might no longer look right. It's not an issue of a binary format changing or something, it's that the skin is saying "put a black line here" (for example), and "here" is no longer where that line should appear. That's not really something it's feasible to provide backward comaptiblity with, unfortunately. That's probably not the only reason, but it is one reason that I've personally experienced while fixing some bugs in Thunderbird's GUI.

      --
      Rock over London, Rock on Chicago. Wheaties: Breakfast of Champions.
  19. Re:Mozilla is a great browser by phalse+phace · · Score: 5, Interesting
    Yes, pop-up blocking is great.

    I often get customers coming up to me and asking what they can do to reduce or stop those annoying pop-up's. Sometimes I'll have to stop and think for a few seconds to understand/remember what they're talking about since Mozilla has spoiled me.

    The first thing I always do is recommend that they download Mozilla and give that a try while explaining to them that I haven't seen a pop-up in over a year.

    Unfortunately, though, most folks (~ 95%) will just tell me that they like/are happy with Internet Explorer, despite its bugs and holes. After another attempt at explaining to them the benefits of switching, I'll just tell them about products such as pop-up stopper and popup defender. It's sad, really, as they have no idea what they're missing out on.

  20. Re:Mozilla is a great browser by Kethinov · · Score: 2, Funny

    Okay while I agree with everything you said, your post seems terribly manufactured. I mean come on, everyone on Slashdot that's been here for at least 6 months knows Mozilla and open source are DaShiet(tm) and surely as someone with a UID that much lower than mine you already knew all this stuff. So do you make these kinds of posts every time there's a Mozilla article? Cause this is the first one I've seen. ;)

    --
    You're right, I wouldn't steal a car. But if it were possible, I sure as hell would download one!
  21. One flaw with Mozilla & Firebird. by zymano · · Score: 4, Interesting

    I was talking to a few members of the development team and asked them when they would implement a faster,better web page caching system like opera but the developers mentioned it would take thousands of lines of new DOM code. They also said if you want faster browsing then just open a new window . I think there is a lack of priorities by the top managers at mozilla. How could making an installer be more important than making the brower faster. Also the fast forward and rewind is a good idea . If you notice ,alot of these direction features are in ADOBE ACROBAT PDF viewers.

    1. Re:One flaw with Mozilla & Firebird. by Alex · · Score: 4, Funny

      I think there is a lack of priorities by the top managers at mozilla. How could making an installer be more important than making the brower faster.

      You haven't quite got your head around this "open source" thing have you?

      Alex

    2. Re:One flaw with Mozilla & Firebird. by falsification · · Score: 5, Insightful
      Mozilla is optimized for tabs.

      Once you've gotten used to 20+ tabs and flipping between them instaneously, watch out. Mozilla is like the crack of the Internet. Highly addictive.

    3. Re:One flaw with Mozilla & Firebird. by wannasleep · · Score: 5, Insightful

      I'll give you one reason: the average (window$) users will give up if the installation is not better than smooth and will never see all the great things mozilla has to offer. Sadly, the average user is used to bearing with slow stuff more than he is to thinking.

      Remember: perception is more important than reality.

    4. Re:One flaw with Mozilla & Firebird. by monkeyfinger · · Score: 5, Insightful
      How could making an installer be more important than making the brower faster.

      I think a proper installer is a very high priority. I'm a linux user and use and I am quite happy using tar, but I've got a lot of friends who use windows and don't have the skills to install software that doesn't have an installer.

      With an installer these people can download and install it themselves and then they can tell their friends, who can do the same. Mozilla usage can increase at an exponential rate. Without the installer mozilla would only be available to the technically savvy and their close friends.

    5. Re:One flaw with Mozilla & Firebird. by fiftyfly · · Score: 4, Informative

      Add in a few nifty settings (force tabs to open in the background, and middle click opens in a new tab) a great mod and a daily reading list and the amount one can quickly & effeciently surf is truly astounding.

      --
      "Sanity is not statistical", George Orwell, "1984"
    6. Re:One flaw with Mozilla & Firebird. by Random832 · · Score: 2, Informative

      no... what he was saying was just that there's no central authority deciding who works on what - whether something's "more important" is irrelevant to how many people are working on it.

      --
      We've secretly replaced Slashdot with new Folgers Crystals - let's see if it notices.
  22. I know I will get flamed for this... by use_compress · · Score: 4, Interesting

    But why not concentrate on implementing IE's version of DHTML? Given, MS doesn't follow set "standards" in this department. But many developers prefer MS's approach and most users (willingly or ignorantly) use Internet Explorer. These two factors cause many sites to support IE exclusively. It is very expensive for companies to implement Mozzila compatible versions of their webpages for the minority of internet users who don't use IE. Why not save everyone a lot of time and money and support Microsoft's version of DHTML?

    1. Re:I know I will get flamed for this... by LizardKing · · Score: 5, Insightful

      But why not concentrate on implementing IE's version of DHTML?

      Because the Mozilla developers will always be playing catchup. Once MicroSoft cottons onto the fact that the Moz people are expending considerable effort in matching IE's DHTML features, they'll most likely start releasing new extensions. As it is, there is a good compromise already in Mozilla. Web pages that don't appear to be standards conforming are rendered in "sloppy" mode, which generally works for IE targeted stuff.

      At the end of the day, I cannot think of a single website that uses IE specific DHTML in a way that makes me yearn for support for it in Moz. The last IE only website I encountered was the Egg online bank one. Their insistence that I hadn't got a recognised browser simply means I got a credit card from somewhere else (Sainsburys as it happens).

      Chris

    2. Re:I know I will get flamed for this... by zonix · · Score: 4, Insightful

      Shouldn't that be:

      But many developers (willingly or ignorantly) prefer MS's approach and most users (willingly or ignorantly) use Internet Explorer. It is very expensive for companies to implement Mozzila compatible versions of their webpages for the minority of internet users who don't use IE.

      I'm tired of hearing this argument! If you just adhere to the standards when creating web pages you'll be just fine. In fact, you'd be better off as your pages will be much more easy to maintain, and you'll benefit greatly from all the available features that come with CSS. Try weighing the cost of maintaining a tag soup IE optimized (ugh!) page against a page using strict standards and the latter will win anytime!

      IE is way behind Mozilla and Opera, it doesn't even support application/xhtml+xml, which is (or should be) used for XHTML. And don't get me started on the XML-declaration, IE chokes on this and throws itself into quirks mode when rendering your content.

      z
      --
      What would an EWOULDBLOCK block, if an EWOULDBLOCK could block would? -- me
    3. Re:I know I will get flamed for this... by globalar · · Score: 4, Insightful

      "Why not save everyone a lot of time and money and support Microsoft's version of DHTML?"

      Which is harder? Designing web pages by a common standard or conforming to one application's twisted implementation of said standard? You don't necessarily save money by developing only for IE. You waste time trying to create interesting ways to mimick features that can be trivial to implement in any compliant browser or simply attempting to figure out what IE will let you do. Remember browser compatibility charts that used to tell you what browser's supported what features? These were nightmarish for a simple markup language and a few CSS features. And so the solution is to just give up on compatibility charts and let MS have its way?

      "It is very expensive for companies to implement Mozzila compatible versions"

      No, no, I think you have it backwards. You are familiar with web standards? IE does a half-baked job of implementing them, makes some mistakes, omits things, and then leaves most of these problems for long periods of time. Oh yes, and some features actually might crash the browser.

      Mozilla doesn't try to make web pages conform to some twisted view of a standard. Rather, Mozilla takes said web standards and attempts to comply with them.

      There is also a principle here which is very important and every one seems to give up on. Open standards are important because they accomplish several things at once:

      1) They promote use of the medium - making a given medium more accessible and beneficial to all involve.

      2) They limit unnecessary complexity/redundancy - this saves everyone time and money.

      3) They keep control away from single-minded interest groups who wish to control users of the medium. In essence, they protect the medium and its users. In the best cases they represent the interests of users and those care most about the medium's community.

      Some people refuse to allow IE to dominate the browsable Internet unchallenged because it will only hurt the community and all involved. IE's dominance has brought apathy to its lackings - everyone knows in many ways it sucks, but the majority of its users are either ignorant, don't care, or are (seemingly) powerless. This in turn has actually warped the perception of the Internet into many things it should not be (a circus for advertising, for one). But even worse, IE has forced many developers to forget web standards and focus on IE and its version of things. In effect, IE says what is standard and what is not and we all obey.

    4. Re:I know I will get flamed for this... by pinny20 · · Score: 2, Informative

      You must have used Egg a long time ago, as I was using Mozilla 1.5 quite happily with it a couple of days ago, with no rendering quirks at all, and no insistence that I use Internet Explorer.

    5. Re:I know I will get flamed for this... by zonix · · Score: 4, Informative
      As it is, there is a good compromise already in Mozilla. Web pages that don't appear to be standards conforming are rendered in "sloppy" mode, which generally works for IE targeted stuff.

      Actually both IE and Mozilla/Gecko (don't know about Opera) have this quirks rendering mode.

      They use DOCTYPE - the first line of the source - sniffing to determine which (X)HTML version the web page is written for. If the page indicates the use of a strict version of (X)HTML, these browsers will render the page in a strict standards compliant mode. Everything will be rendered according to the strict standards as proposed by The WWW Consortium. Your pages will look the same both in IE and Mozilla, however don't be fooled by IE's relaxed attitude towards block/inline content - do read up on this in the specs. If you preview your pages in Mozilla first you will save a lot of time, because it's not as forgiving when you make mistakes.

      In quirks mode you can use all the dirty tricks from the old days. Everything will look horrible accros different browsers, and the source will be next to unmaintainable!

      The quirks/strict standards modes are triggered by these doctypes respectively:

      Quiks mode:

      HTML 3.2
      HTML 4.01 Transitional
      HTML 4.01 Frameset
      XHTML 1.0 Transitional
      XHTML 1.0 Frameset

      Strict standards mode:

      HTML 4.01 Strict
      XHTML 1.0 Strict
      XHTML 1.1

      I'd advise everyone to write (X)HTML to the strict versions and make the www a better place to be for all of us.

      z
      --
      What would an EWOULDBLOCK block, if an EWOULDBLOCK could block would? -- me
    6. Re:I know I will get flamed for this... by John_Booty · · Score: 4, Informative

      At the end of the day, I cannot think of a single website that uses IE specific DHTML in a way that makes me yearn for support for it in Moz.

      I agree 100%. I've been using Mozilla and Firebird as my primary browsers for several years... never do I hit sites that make me "need" Internet Explorer.

      Occaisionally I'll hit a site with DHTML menus that render a little funky in Mozilla because they weren't coded right, but I never hit any sites that "need" IE.

      If the "compatibility" thing is what's holding anybody back from trying Mozilla or Firebird, then... by all means... you're really not missing anything, guys!

      --

      OtakuBooty.com: Smart, funny, sexy nerds.
    7. Re:I know I will get flamed for this... by neocrono · · Score: 5, Informative

      (don't know about Opera)

      Here is Opera's rendering mode "strategy."

      Having recently made an excursion into the world of XHTML 1.1 web design, I have to say, it demands so much of your code, you'll never look at tag soup the same way again. But it's worth it. It took a while, I adjusted, and will never give an (X)HTML document that doesn't validate* to the browsing public again. I strongly urge all of you to put forth the effort to check your pages and read up about web standards (here) as well.

      If only there were some way to get the same from the 8,419,528,073 animated GIF-loaded, Frontpage Express, Geocities-hosted messes elsewhere on the web.

      *: Don't forget to check your CSS for validity as well. :)

    8. Re:I know I will get flamed for this... by Psiren · · Score: 2, Insightful

      I'm tired of hearing this argument! If you just adhere to the standards when creating web pages you'll be just fine.

      If you adhere to the standards it will work just fine in Mozilla. It might work in IE, but quite probably won't if you're doing any CSS2 or some CSS1. IE plains sucks when it comes to standards support.

      This is both a blessing and a curse for Mozilla really. On the one hand it's good that there is an open source browser will full support for the latest standards, while MS still don't have one. On the other, since MS don't plan on releasing any updates to IE until Longhorn is released, we'll be stuck with this shit version for years to come. And going by past evidence, I doubt they'll get a standards compliant version out even then.

    9. Re:I know I will get flamed for this... by mphase · · Score: 3, Informative

      "Everything will be rendered according to the strict standards as proposed by The WWW Consortium [w3.org]. Your pages will look the same both in IE and Mozilla" Not quite true, that is what the strict or standards modes are intended to do (and partially do) but realistically certain things are going to be treated differently even by browsers in standards mode. For example floats are treated much differently by IE then in Mozilla even if both are in rendering an XHTML 1.1 page (personal experience with my own site).

    10. Re:I know I will get flamed for this... by zonix · · Score: 4, Informative
      For example floats are treated much differently by IE then in Mozilla even if both are in rendering an XHTML 1.1 page (personal experience with my own site).

      That's probably because IE's CSS implementation is a wee bit lacking. I've run into that float problem myself, but I got around it.

      There are ways around other IE CSS lackings as well, e.g. IE 5 had problems the w3c's _recommended_ way of centering text by specifying both left and right margins as 'auto'. It's fixed in IE 6, but I believe you could put in extra (well, redundant) rules in your style sheet to satisfy IE 5. However it's a bit ugly and unfortunate that you have to do it.

      If you check out W3c's pages, even they will sometimes present different style sheets depending on your browser. The CSS page itself is a good example. Try IE and Mozilla with this one.

      In any case, these lackings on IE's part will hopefully be fixed in the future, which means if you follow the standard IE will ultimately have to follow you.

      z
      --
      What would an EWOULDBLOCK block, if an EWOULDBLOCK could block would? -- me
    11. Re:I know I will get flamed for this... by rudy_wayne · · Score: 2, Insightful

      Which is harder? Designing web pages by a common standard or conforming to one application's twisted implementation of said standard? You don't necessarily save money by developing only for IE.

      You are familiar with web standards [w3.org]? IE does a half-baked job of implementing them...........

      Mozilla doesn't try to make web pages conform to some twisted view of a standard. Rather, Mozilla takes said web standards and attempts to comply with them.


      You're right, but you're missing the point. Consider the facts:

      1. MSIE is non-compliant with W3C standards.
      2. As a result of #1 (and MSIE's 90% market share), many millions of web pages have been created to conform with MSIE features rather than W3C standards.
      3. The W3C doesn't follow their own rules. A while back, some guy from Finland decided to do a survey of web sites run by W3C members, and out of 400 sites studied he found that 95% were not fully compliant with W3C standards because they had been designed with various IE-specific features.

      So the real question is:

      Which is harder: Getting tens of millions of people to re-design their broken, stupidly coded, non-W3C compliant web sites. Or, designing a browser that can display their broken, stupidly coded, non-W3C compliant web sites.

  23. Most of my friends have never heard of Mozilla by FatAssBastard · · Score: 4, Insightful

    I only have a few computer nerd friends. All my other friends' eyes just glaze over when I try to explain the benefits of using Mozilla. So I don't even try any more.

    Hey, if they love popups (they aren't usually even aware of the Google Toolbar, for instance), and enjoy the occasional virus or homepage hijacking, they can help themselves.

    How sad that most people just don't really seem to care. :(

    --
    /.: why the hell am I here?
    1. Re:Most of my friends have never heard of Mozilla by pgr0ss · · Score: 2

      Yeah, the people I tell usually just ask what the point is since IE is already there. Also, they complain that it's slower than IE. For them, popup blocking, tabs, etc. just don't really matter. Personally, I am willing to trade a little speed for a whole lot of features.

    2. Re:Most of my friends have never heard of Mozilla by monkeyfinger · · Score: 3, Informative
      Maybe trying to explain things to them isn't the best idea, not every one will grasp something unless they see it. It may be easier for them to comprehend if you actually go round to their place and give them a demo.

      I personally would set people up with firebird. It's a slick looking browser and that will impress a lot of people. If you sit them down and gently guide them through tabbed browsing it will all make sense. Popup blocking can be demonstrated by challenging them to find a website with a popup (if they like to look at porn they will notice a huge improvement).

    3. Re:Most of my friends have never heard of Mozilla by zsau · · Score: 2, Funny

      Break into their houses at night and install Mozilla. Make it the default browser. Give in the IE icon.

      --
      Look out!
  24. Flash format IS open. by MelloDawg · · Score: 2, Interesting

    http://www.openswf.org/

    There are lots of third-party apps that generate Flash files.

    --
    /. is irrelevant.
  25. yes you will get flamed for this by logic7 · · Score: 3, Informative

    because your statement is false. I work at a company which develops applications for web browsers, so there is a lot of Javascript/DOM/DHTML etc involved. The current browser generation is not nearly as difficult to handle as it was in the bad old times of Netscape4/IE4. We have a neat little js-framework that handles the differences between IE and Mozilla and most code works on both browsers without heavy modification.

  26. Web Editor by eternal_soul · · Score: 5, Informative

    Am I the only one in here that do not type out my web pages in a text editor? I happen to prefer the WYSIWYG web editing of Mozilla, which is missing from the Firebird releases. I, for one will be very unhappy to see the main branch of Mozilla discontinued just because of this.

    --
    Time flies like an arrow, Fruit flies like a banana.
    1. Re:Web Editor by koekepeer · · Score: 2, Informative

      there is an effort by a guy named daniel glazman to develop a standalone composer, to complement firebird and thunderbird.

      so you'll have your precious composer! (no sarcasm intended, although i prefer editing suites like quanta, bluefish, screem)

      the general idea is (i think) that development of mozilla in standalone applications will be more flexible, easier to keep bugfree etc.

      of course this provides us with more choice (do i want this component or not) which is always good IMHO

    2. Re:Web Editor by w_crossman · · Score: 5, Informative

      There is going to be a standalone composer soon, called Nvu. It is based on Composer and will fall under an open source license, and Lindows is footing the bill. I really don't think we have anything to to be worried about! If you're curious, see their website.

  27. DOM performance by groomed · · Score: 2, Interesting

    They should fix the abysmal DOM performance some time. Simple DHTML applications or even plain document.write() hacks can bring Mozilla to its knees as it labors to add nodes to the document.

    1. Re:DOM performance by Nadir · · Score: 3, Informative

      Actually you should check this great page which provides performance data for a few DOM operations. http://www.quirksmode.org/dom/innerhtml.html

      --
      --
      The world is divided in two categories:
      those with a loaded gun and those who dig. You dig.
  28. Re:My one complaint... by BZ · · Score: 2, Informative

    It's pretty simple to understand... Just look at the checkin list for the relevant timeframe (http://bonsai.mozilla.org/cvsqueryform.cgi).

    Lots of under-the-hood stuff that you may not see, but 1.6 is about 10% faster than 1.5 at rendering web pages. ;)

  29. NTLM proxy by alien_blueprint · · Score: 4, Informative

    Just a quick comment for those stuck with NTLM at work. I run a local NTLM proxy server so I can run whatever browser or HTTP tool I like on whatever OS I need. I just point my browser at the proxy and it just works.

    The proxy I use is written in Python, is small, and is really easy to install. NTLM Authorization Proxy Server.

    Since you are authenticating with your user name and password, from your machine, and you are still actually going through the company web proxy just like IE would, there's absolutely no logical reason for the local "preventers of information services" to complain. At least, in my case, they haven't been able come up with an actual reason yet that hasn't been easy to dismiss. Not for want of trying, though ...

  30. Re:Firebird 0.8 by showdax · · Score: 5, Informative

    Well, if you need to know how far away, you could check out http://www.squarefree.com/burningedge/ for a nice summary of the 'nightly' activity. If you want to see 'who changed what in what file and when' in any release, just check http://bonsai.mozilla.org/. Not as easy to summarize that yourself, but when I was into the nightlies, I loved watching that. The rate of progress is phenomenal.

    --
    --- March, milde, march!
  31. Man by Nebajoth · · Score: 4, Funny

    Does anybody else find it frightening that we have web browsers with automatic language translation? I mean, its awesome! But... where the hell was I when the world got all Star Trek?

    1. Re:Man by Haeleth · · Score: 3, Insightful

      It's useful for some, perhaps, but I don't speak gobbledygook very well. I'll start getting excited when they release a version that translates into English.

  32. Re:When do the versions roll over, I wonder? by SEE · · Score: 2, Informative

    Rot13? Try http://www.pinkroom.biz/owl/minirot13/

    Why this hasn't been added to the codebase, I have no idea.

  33. ooops ... :) by jopet · · Score: 2, Informative

    of course I meant that Mozilla still suppoerts W3C standards better ... though there are some CSS things that work better in IE. MS is finally slowly catching up.

  34. Re:I don't understand by superyooser · · Score: 2, Informative

    1.5.1 exists only for Mac OS X. The latest stable version for all other platforms is 1.5.

  35. Re:I don't understand by The+Clockwork+Troll · · Score: 4, Insightful
    Does "alpha" mean bug-free? No.

    Does "beta" mean bug-free? No.

    Does "stable" mean bug-free? No.

    These labels have nothing to do with optimizations or improvements; they are reflections of a team's comfort level with a products' defects and limitations.

    --

    There are no karma whores, only moderation johns
  36. OS X Mailsound still not working. by dafdaf · · Score: 2, Interesting

    Wow ! And after years of development, playing a .wav file if new mail arrives, still doesn't work.

    But besides that, Mozilla is by far the best piece of software on my computer(s). - I've been using it since the early milestone releases (on Linux) and will be very sad once the Mozilla suite will be discontinued...

    --
    To error is human, to forgive, beyond the scope of the OS.
  37. Does this include the box model? by Afty0r · · Score: 2, Insightful

    Do IE and Mozilla treat the box model in the same way? (Example : try setting a fixed width box with a border, then adding some padding to it - it will currently look different under each browser)

    If it does, then cool, but I'd be surprised.

  38. Re:firebird by Deusy · · Score: 2, Funny

    I hope they develop firebird into a PIM suite

    I dunno... I a bit sceptical about developing a web browser into a PIM suite. Surely that'll mean massive work underneath the hood.

    On a more serious note, I see what you mean. Thunderbird would be amazing if it got task, scheduling, and contact support.

    --

    Free Gamer - Free games list and commentary

  39. Rough Changelog for Mozilla 1.6 Beta by ANicknameSimilarToMi · · Score: 2, Informative
    If you're interested in what got fixed during this cycle, see the Changelog for 1.6 Beta (about 375 issues)

    • http://www.mozilla.org/releases/mozilla1.6b/chan gelog.html
  40. Appease and Beat the Rush by Anonymous Coward · · Score: 3, Funny

    I for one welcome our new Mozilla 1.6 Beta overlords.

  41. Maybe the regressions? Or profile migration? by Anonymous+Brave+Guy · · Score: 4, Interesting

    There were several unfortunate bugs that crept in with 1.5, and as far as I'm aware haven't been fixed yet, e.g.,

    • Mozilla mail pops up asking some people for their password all the time, even if they tell Password Manager to remember it
    • Gecko still renders some page layouts (like Slashdot) badly first time out, IIRC due to some bug with the box layout code
    • they've messed up a couple of things with the CSS code while trying to fix other bugs, e.g., margins around HR tags don't work properly now.

    These are annoyances more than critical faults, but bring down the general quality. Given that the functionality used to work until 1.3 or 1.4 in each case, they're also regressions, which suggest weaknesses in the code introduced inadvertently and best fixed before building on it further for Thunder/Firebird.

    It could also be the issue of profile migration. AFAIK, there are still no solid tools available to move a profile from Moz to the next generation alternatives, nor any easy way to move back if you don't like the change. The Thunderbird download pages are covered in warnings about this. If you're relying on Moz for more than toy use, for example if you have thousands of e-mails filed away that you want to keep, that alone might be enough to prevent you considering an upgrade, and thus to justify continued development of the original Mozilla tools in parallel with the new work.

    --
    If you disagree, post your argument. (-1, Overrated) isn't your personal censorship tool for views you don't like.
  42. Re:It's because SVG sucks ass by CaptnMArk · · Score: 3, Funny

    And all those clean looking blank pages saying just "skip intro".

  43. Re:When do the versions roll over, I wonder? by Mr_Silver · · Score: 2, Insightful
    Why this hasn't been added to the codebase, I have no idea.

    Because it's a pointless thing that is only relevant to the 0.01% of the population that a) have Mozilla and b) read that newsgroup.

    Far better for it to be in a module. Then if you want it, you can install it, rather than bloating out the main application with something that the majority of people won't ever use or even understand the need for.

    --
    Avantslash - View Slashdot cleanly on your mobile phone.
  44. Re:SVG support-Petard hoisting. by interiot · · Score: 2, Informative
    Look on this page under "Status".
    • Big areas of the SVG specification where we're still lacking include clipping, filters and declarative animations.

    You can see screenshots of what the patched Mozilla is capable of here. It can do basic drawing of shapes. However, without filters (eg. embossing, shadows, etc) or animation (eg. smoothly interpolate a color or shape from one state to another), much of the really sexy parts of SVG aren't available. And if you have a stock browser, none of SVG will be available until the code's good enough to bring in.

  45. Re:SVG support - built my own by wowbagger · · Score: 2, Interesting

    In order to check out the SVG support, I build my own image of Moz from the mainline CVS branch a couple of weeks ago.

    The SVG isn't included for good reason - in its current state it is next to useless. Moz natively supports SVG right now as much as Microsoft natively supports the POSIX API - just enough to claim it, not enough to be useful.

    However, IF you have the machine and the connection to do so, I suggest building your own - they have greatly improved the build process. Compiling moz with "-Os -march=athlon-xp -mfpmath=sse,376" has greatly improved the speed of Moz on my machine - but YMMV.

  46. Re:It's because SVG sucks ass by horza · · Score: 4, Informative

    It's because SVG sucks ass and designers (myself included) are the ones who bring you vector graphics over the web. They decide. Simple as that. FlashMX is THE standard for vector design - not to mention a complete development environment to make all those nice applications and games.

    SVG appears to be far superior to Flash for Vector graphics, especially the way it's so easy for a scripting language to modify it on the fly. FlashMX isn't the standard for vector design, it's a tiny niche market for web designers like yourself. The vector graphic designers include everybody on the face of the planet that uses an application such as Adobe Illustrator.

    When SVG becomes de facto, we will see small web design firms become far more productive:
    * designer fires up Illustrator (or whatever) and knocks up a pretty design
    * designer points out that his texts COMPANY_NAME_HERE and SLOGAN_HERE need to be dynamic
    * client-side programmer takes 10 seconds writing a script that reads in the file, does a str_replace() with the company details in the database, and spits it out

    Thankfully all the menu buttons can be done this way, which wastes a lot of our designers time and soaks up bandwidth for no practical purpose. The alternative of Flash for buttons is not good as it cuts out those without the plug-in, and people losing or not sending the source means we have maintenance troubles.

    Phillip.

  47. Not the Unix way by wowbagger · · Score: 3, Interesting

    I don't understand why Mozilla has ANY form of disk caching built in in the first place - that is not the way of Unix.

    Let a seperate program do the disk caching (e.g. Squid). Let Moz and any other program use that program. Thus, everybody benefits from the cache.

    Just like in the latest released of libresolve (the DNS library for *nix systems) now has the "lightweight resolver" which is a small caching resolver library, so that applications that stupidly keep asking to resolve the same address don't load down the nameservers.

    The way of Unix - "small, sharp tools" or "one job, one program" is not just for geeks - it makes for a more robust system as the programs can be optimized to do what they do VERY WELL.

    1. Re:Not the Unix way by Tack · · Score: 4, Insightful
      I don't understand why Mozilla has ANY form of disk caching built in in the first place - that is not the way of Unix.

      You might not know this, but Mozilla doesn't just run on Unices. It also runs on Windows, Mac OS, and god knows what else. Most of what Mozilla does is not the way of Unix, mainly for the sake of being cross-platform.

      Anyway, if you're interested in "small, sharp tools" or "one job, one program," you should look at Firebird and Thunderbird. You might be interested in knowing that this is the direction Mozilla is heading. So the Moz dev team would appear to agree with you there -- don't hold your breath about losing the disk cache, though.

      Jason.

    2. Re:Not the Unix way by wowbagger · · Score: 3, Interesting

      Actually, my point was that by creating a seperate cache program, they could bring the benefits of this to ALL platforms, *nix or not.

      And by the way - MacOS is Unix.

      The biggest single mistake Netscape made back in the day was to NOT realize that by providing a set of small sharp tools to the Windows programmers, they left the market open to Microsoft, who did exactly that. This is something they are trying to correct with Mozilla, by providing things like Gecko and the Netscape portable runtime libraries, but if they were to provide a unified disk caching library they could begin to provide a real benefit to Windows users.

  48. Re:It's because SVG sucks ass by Performer+Guy · · Score: 2, Interesting

    Sorry, it is not superior. There are ambiguities, it relies on SMILE for it's animation and SMILE is badly specified and overly complex. The implementation issues and ambiguities mean that very simple animations produce different results on different browsers. The complexity means that there aren't a lot of very functional implementations because it's a big job to implement what should be a simple format.

    The whole thing is a wasted opportunity.

  49. Re:Mozilla is a great browser by mbourgon · · Score: 2, Funny

    My dad was having the same problem - I moved him to Moz, since setting up a (1)Pop-up Blocker and (2) Junk Mail filter, via him on the phone, was more involved than just having him download/install Moz. He loves it - it moved over all his settings from IE, no more problems and no tech calls.

    --
    "Sometimes a woman is a kind of religion, she can save your soul & set you free from all your sins" - Bad Examples
  50. Mozilla is still bad with standards by axxackall · · Score: 3, Insightful
    Two big problems I see with Mozilla's way of implementing protocols: Why Mozilla developers think that Calendar and Chatzilla (which has nothing to do with web-browsing at all, and by the way it's implemented anyway so badly that nobody use it) are more important for web-browsing than a complete implementation of core web-browsing protocols?

    Maybe at early 90s it was ok that that the web-browsing is a one-way communication when you only read and download the content. But it's not true anymore (perhaps since the dot-com bubble?). Today the web-browsing is almost always a two-way communication: people are answering web-forms and uploading files all the way.

    I suggest Mozilla developers to wake-up, to free themselves from old AOL cultural traditions (remember? AOL still tinks that the internet access == dial-up 56K modems!), and to redistribute their resource accordingly to real priorities. Stop wasting your time on developing ChatZilla and Calendar (really useless components). Instead, devote those resources on FTP upload and HTTP WebDAV.

    --

    Less is more !
    1. Re:Mozilla is still bad with standards by axxackall · · Score: 2, Funny
      *You* havn't figured out how free forums work yet have you?

      Here's a hint: you don't tell me what to criticize or not and in return I don't tell you what I am telling you now!

      --

      Less is more !
  51. Re:Mozilla is a great browser by jmelloy · · Score: 2, Funny

    My dad was having the same problem at his work. I recommended he download Mozilla or Firebird.

    The next day, he said, "So today I went through all my links and deleted the ones I never use. Now I don't get anywhere near as many popups."

    I still don't know what he actually did.

  52. It's so impossible that... by Futurepower(R) · · Score: 2, Insightful


    "get binaries' checksums to match the old binaries' checksums (nigh on impossible, given how md5 hash works)"

    It's so impossible that someone who could do it might win a Fields medal.