Table of topic groups > Front page of CSS-guide > General info > Functionality of my pages with different browsers > Functionality of my pages with Netscape/Mozilla browsers (section 4/4)

Sections of page:

First section

Previous section

Functionality of my pages with Netscape/Mozilla browsers

Topics

• Common
• Browser specific hints
• Known problems

Common

Mozilla 0.9, Netscape 6.1+ and other at least as new Mozilla Gecko browsers render my CSS-site on screen almost as designed, in fact the best. The reason, why I can say at this way is that is is possible to create for new Netscape/ Mozilla browsers fixed positioned dynamic links, where also sub-menus are fixed and the work in all situations. I have used in the screen presentation of this site following following features, which are not supported in Opera 6.0x and MS IE 6.0 for Windows (they are however supported in Opera 7.x):

1. The dynamic pseudo-class :focus (this pseudo-class shows the last activated link).
2. Alternative style sheets (rel="alternate stylesheet" + title="..."). I use them only demonstrating the functionality of them. Because they don't actually help reading sites, they don't make the functionality of the CSS-site better with other browsers.

Browser specific hints

• This site works best with Netscape 6.1+ and evaluation version of it, for example with Mozilla 0.9. With these browsers the main navigation element is fixed.

Known problems

New Mozilla Gecko browsers don't have many such missing features, which limit Web-designing. I list however two:

• In newest Gecko browsers fixed positioned dynamic menus caused distorted rendering of the main content when pages were scrolled. That's why I took of them fixed positioning.
• Some versions don't keep the correct positioning (these browsers are however the only browsers.
• I could 't however create dynamic sub-menus for Netscape 6.1+ only by using CSS (look out models), because they cause in Netscape 6.0 terrible result. I don't know any possibility to separate Netscape 6.1+ and Netscape 6.0 from each others. Indeed it is more reasonable to create DHTML/ DOM-menus, which work properly designed also in Opera and MS IE browsers.
• Controlled page breaking features for printing don't work in my tests except in newest versions of Mozilla and also in those browsers partially. According to an e-mail page breaking features for printing work starting from Mozilla 1.0 around 17.03.2002. According to an e-mail from a volunteer contributor of Mozilla builds Netscape 7.x browsers are the first Mozilla 1.x based Netscape browsers, which support page break properties. First versions of the Netscape 7.x series are in the market. The last 6.x series version in 14.07.2002 was Netscape 6.2.3, which base on Mozilla 0.9. Mozilla 0.9 series doesn't support paged media at all and then page breaking properties. The printing of Mozilla 1.1 would be as good as it is in Opera if it would support page-break-inside:avoid.

Also in newest versions is some features, which work bad. Below is a list of some remarkable problems in my sites with new and old Netscape browsers:

• Mozilla Gecko browser show font sizes like (if the standard-compliant mode is on) MS IE 6.0 for Windows almost according to the CSS2 recommendation. That means however, that in default setting they show the basic font size a little bit smaller than Opera and MS IE 5.x for Windows. Don't however change the font size from the quick menu, because links in the main navigation are set to work only with the zoom factor 100% (If you want to see the basic font size the same as it is in Opera and MS IE 5.x for Windows browsers, set the default font size to 18 pixel).
• If pages have IFRAME elements which are going to hide when the document will be printed, Netscape 6.1-6.2.1 browsers crash (according to an e-mail from the Mozilla org this bug is fixed in the newest Mozilla builds, but I don't know which Netscape 6.x version this will be fixed). Normally these browsers should not crash. Netscape 6.0 prints IFRAME element even if they should not print. The browser doesn't however crash.
• The top margin of the main content of the page might be incorrect with Netscape 6.2.1 Reloading those kinds of pages might help.
• At least until Netscape 6.2.1/ corresponding Mozilla browsers links inside fixed positioned elements might move, when they are clicked and they might need to click twice (I don't have found this problem in newest builds).
• If I would have used dynamic sub-menus only by using CSS, :focus would not work exactly as expected (look at models).
• Netscape 6.x/ Mozilla 0.9 can't always position correctly the IFRAME element.
• The presentation of the main menus are with Netscape 6.x/ corresponding Mozilla browsers a little bit incorrect.
• Netscape 6.0/6.01 can't position the main navigation as fixed.
• Netscape 4.0x doesn't understand the attribute id as an anchor in a page and then as an unique identifier for the href attribute. Because of this reason most links inside pages don't work. For example the link (in the page Preface and important information) <a href="#Copyright">Copyrights</a> together with <h3 id="Copyright">Copyrights</h3> doesn't work.
• The presentations of my sites are relative poor with Netscape 4 series browsers even if I have tried to make them quite good for Netscape 4.x. Because I know problems, I don't accept any complains, which concern the presentations of my sites with Netscape 4.x.
• Because Netscape 4.04 crashed in my index page and after clicking some links in my CSS-site, such 4.x series Netscape browsers, which version number is smaller than 4.70 have simpler CSS.

Sections of page:

First section

Previous section