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

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

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

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

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

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

  9. 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!
  10. 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.
  11. 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.

  12. 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. :)

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

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