SillyDog701

[Josh]

The FTP Server is your friend.

[Hendikins]

Now with <marquee> support! boo! hiss!

It's up on the releases page at mozilla.org too...

[Antony]

Mozilla Release page: http://mozilla.org/releases/
Mozilla 1.1 Release Notes: http://mozilla.org/releases/mozilla1.1/

What's New in Mozilla 1.1

• Improved application and layout performance
• Improved stability
• Improved Web site compatibility
• Improved CSS, DOM and HTML standards support
• Distinct window icons for the different Mozilla applications (artwork contributed by Grayrest).
• Mozilla can now trigger MS DUN when started without a connection.
• Fullscreen mode for Mozilla on Linux (press F11).
• Browser tabs now close left to right (they used to close right to left).
• The tab bar now has a button for creating new tabs.
• All Search entry points now use your default search engine.
• Download Manager has been enabled as the default download view (with many improvements)
• Autocomplete in the addressbar has more intelligent completion.
• The Linux File Picker has improved filtering and a new directory button.
• File extensions more accurately handled in downloads and we save the correct files when saving complete Web pages
• Drag and drop support has been greatly improved.
• View selection source: Context clicking on a selection now lets you view the HTML source for the selected area.
• Page info displays more page info with improved General and Media tab content.
• New button in prefs for making Mozilla the system default browser on MS Windows
• MathML is now enabled for Mozilla on Macintosh (it was already available on win and linux).
• Mozilla now takes advantage of Quartz rendering for users of Mac OS X 10.1.5
• Better Bi-Di Arabic and Hebrew support including improved layout of Arabic pages on Linux and other platforms without their own Arabic shaping support.
• We have new layout performance enhancements targeted at DHTML.
• Mozilla now has support for the display of XBM images.
• Image and plug-in blocking for Mail & News
• Mozilla allows you to view HTML mail messages as plain text.
• You can now quote the current message in a Mail compose window with Quote Original under the options menu.
• The JavaScript Debugger has gone through a major development cycle. It now sports a palette of nine views which can be rearranged within the main window or docked in separate floating windows. It is also possible to create user-defined views and commands directly with JavaScript. More details are available in the FAQ, newsgroup, or IRC channel.
• Chatzilla has improved tab completion and can now join channels with Japanese names.

I did not see any words about <marquee>

[Hendikins]

• Improved Web site compatibility

See Bug 156979.

[DJGM]

Support for MARQUEE has been there since 1.1b, as far as I'm
aware. If you go to any web page with MARQUEE tags in them,
they will actually work in Mozilla 1.1 (under Quirks Mode) and
more or less any earlier builds of .1 since 1.1b was released.
I agree that it's not good, that Mozilla has started to support
proprietary tags, but as long as they don't make a habit of
it and introduce support for other non-standard elements,
particularly, other MSHTML proprietary HTML extensions,
then I might just let them off on the MARQUEE issue!
(MARQUEE support was added for compatibility with
certain Chinese sites that have been unsuccessfu-
lly "evangelized" to support W3C standard HTML.

(All is explained in the aforementioned Bugzilla
bug #156979, with quite a lengthy discussion on
the advantages and the disadvantages of support
for this particular MSHTML specific non-standard tag.)

As for Mozilla supporting the god awful BLINK tag, which IMO,
was Netscape's biggest faux pas prior to the 6.0 disaster area!

[Antony]

All right, MARQUEE is supported, how about some good old Netscape's tags...
one of the best one, (not so famous) <MULTICOL> (NS 3 to 4).
Quoted from Danny Goodman's Dynamic HTML - The Definitive Reference.

A Navigator-specific element that renders its content in any number of evenly spaced flowing columns on the page. The way this element flows content might remide you of a desktop publishing program that automatically flows long content into column space that has been defined for the page. There is no equivalent for this element in HTML or Internet Explorer, but the columns style sheet attribute is defined in CSS2.

Note: I don't see columns in CSS2 has been supported.

[Hendikins]

Support for MARQUEE has been there since 1.1b, as far as I'm
aware.

It didn't make it in to 1.1b, but was added very shortly after it.

[Mega\]

I like the <LAYER> tag....

[Shark Daddy]

The really important thing is not that MARQUEE is supported, but rather that it is supported in Compliance Mode. You are correct about part of the reasoning behind MARQUEE being put in, DJ, but if that was the sole reason, MARQUEE support would only go on at certain times. This is a case of Netscape interests taking over a bug and checking it in. Not that that's wholly bad.

CSS2 is a while in coming to Mozilla. In fact there isn't very much activity surrounding CSS2, other than bugs about how Mozilla handles certain part of CSS2 wrongly. There isn't even a CSS2 tracking bug. This doesn't mean it won't come in the near future, but I haven't seen much in Bugzilla, meaning even in the Mozilla community, demand isn't all that high. Antony, the release notes are pretty vague and misleading; if you really want to know what's going on, you have to read and work on bugs.

[Antony]

Antony, the release notes are pretty vague and misleading; if you really want to know what's going on, you have to read and work on bugs.

You don't want me to bring you back to the famous topic, right?
http://sillydog.org/forum/viewtopic.php?t=113

[Hendikins]

The really important thing is not that MARQUEE is supported, but rather that it is supported in Compliance Mode. You are correct about part of the reasoning behind MARQUEE being put in, DJ, but if that was the sole reason, MARQUEE support would only go on at certain times. This is a case of Netscape interests taking over a bug and checking it in. Not that that's wholly bad.

*groan* We've had this argument over and over and over again...

I'm anti-marquee and even *I* am starting to get sick of it!

[Shark Daddy]

Don't get me wrong Hendikins, I don't like MARQUEE either, but it is at least partially needed IMO.

[DJGM]

The MARQUEE tag is NOT supported in "standards" mode, simply because it
is not part of any recommended web standard. While this tag is supported
by Mozilla, and possibly also the forthcoming N7.0 final, it will ONLY ever
be supported in "Quirks" mode. Apparently MARQUEE support isn't even
switched on by default, so as long this move by Mozilla to support it does
not help promote the unnecessary use of it by website developers, to be
really honest, I don't really see it as much of an issue.

Also, I don't want to see Mozilla, or any browser products based upon it,
to start including support for other non-standard and/or prorietary tags,
no matter whether such tags were created by Netscape or Microsoft.

The day that Mozilla starts to support nonsense like LAYERS and other
stuff that was created specifically for NS4.x and versions of IE prior to
version 5.0, is the day that I might reluctantly consider leaving Mozilla
behind, and instead adopting Opera as my primary web browser.
I sincerely hope that is something that will NEVER happen.

[Hendikins]

The MARQUEE tag is NOT supported in "standards" mode, simply because it
is not part of any recommended web standard. While this tag is supported
by Mozilla, and possibly also the forthcoming N7.0 final, it will ONLY ever
be supported in "Quirks" mode.

Incorrect. It's in standards mode.

See Bug 159839 - move <marquee> into quirks mode (Resolved WONTFIX)

Apparently MARQUEE support isn't even switched on by default, so as long this move by Mozilla to support it does not help promote the unnecessary use of it by website developers, to be really honest, I don't really see it as much of an issue.

Incorrect. It's switched on by default. Have a look at say, this site with Mozilla 1.1 and a fresh profile.

Also, I don't want to see Mozilla, or any browser products based upon it,
to start including support for other non-standard and/or prorietary tags,
no matter whether such tags were created by Netscape or Microsoft.

Agreed - within reason. It is a web browser after all. I don't think <MARQUEE> is within reason, however.

The day that Mozilla starts to support nonsense like LAYERS and other
stuff that was created specifically for NS4.x and versions of IE prior to
version 5.0, is the day that I might reluctantly consider leaving Mozilla
behind, and instead adopting Opera as my primary web browser.
I sincerely hope that is something that will NEVER happen.

Anyone for document.all?

Quite a few people are thinking of jumping ship over <MARQUEE>. It's a very sensitive topic...

[Mike of Sheffield]

Well, having downloaded and installed Moz 1.1 (thanks Fulvio Antony and Shark Daddy) I can honestly say I'm impressed with it.

The browser works a treat and so far the mail is good too - I'll take a little longer to pass final judgement there as I've had problems with mail progs before. But already it is allowing me to post mail from Hotmail - which NS6.1 never did (I had to go to IE5.5 for the privilege!). And it reads HTML emails from one particular source, which NS6.1 consistently showed as pages of garbage (yes I did have HTML enabled, and other HTML mails came through OK).

And at 9~10MB download instead of 30+MB it is definitely more practical.

Personally I couldn't give a s**t whether it is compliant with MARQUEE or not if it works properly and lets me do/visit all I want to.

Mike of Sheffield.