More advice for the full screen mode.
Sivut toimivat riittävän hyvin MS IE 4.0+, Opera 5.x+, Netscape 6.0+/ vast. Mozilla ja Konqueror 3.x selaimilla. Yleisesti ottaen sivut toimivat parhaiten uusimmilla Opera selaimilla. Sivujen toimivuus vanhemmissa selaimissa on heikko, erityisesti Netscape 4.x kohdalla.

I list below all topic groups, which I have done according to subjects, which they handle. You can return to this topic group by using this menu and the link Table of topic groups on the top of the each page.

Netscape 6.x+/Mozilla Gecko related problems

Netscape 6.0 has much worse CSS-implementation than newer versions and Mozilla 0.9+. It doesn't support position:fixed. It might need is some circumstances an own CSS. Below is an example of way how to separate different Netscape/Mozilla versions from each others on the base of the date (Build ID) of the browser.

<script type="text/javascript" language="Javascript">
Gecko = (navigator.product == ('Gecko'))
Date1 = (Gecko && parseInt(navigator.productSub)>=20020728);
Date2 = (Gecko && parseInt(navigator.productSub)<=20020727);
if (Date1){
document.writeln('\<lin'+'k\ rel=\"stylesheet\"\ type=\"text\/css\"\ href=\"..\/Css\/MozillaNewest.css\"\ media=\"screen\"\ \/\>');}
if (Date2){
document.writeln('\<lin'+'k\ rel=\"stylesheet\"\ type=\"text\/css\"\ href=\"..\/Css\/MozillaOlder.css\"\ media=\"screen\"\ \/\>');}

In this example the "separator line" of browsers is in certain sub-versions Mozilla 1.1/ Netscape 7.0. For example experimental supported CSS3-implementation -moz-opacity crashed Netscape 6.0 and worked bad in Netscape 6.1 level Mozilla and Netscape 6.2.1. Because of that and another reason set in my CSS-file one separator line to the point above (you can study a source code fragment[S], which I have used).

The dates (Build ID) and corrersponding Mozilla versions of the Netscape 6.x+ are following:

DevEdge: Netscape Gecko User Agent Strings; Mozilla org.: user-agent strings.

Instead of the Build ID it is possible to detect Mozilla Gecko browsers accorind to the version of Mozilla. Below are two string of Mozilla browsers and a possible contition in order to detect those browsers:

Netscape 6.2.1:
Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.4) Gecko/20011128 Netscape6/6.2.1
Mozilla 0.9.4:
Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.4) Gecko/20011128


Indeed that kind of string doesn't work with Netscape 6.0 because it inform the corresponding Mozilla version differently as you can see from the string of Netscape 6.0 (I put below the string some possible detection strings):

Mozilla/5.0 (Windows; U; Win98; en-US; m18) Gecko/20001108 Netscape6/6.0

navigator.userAgent.indexOf('m18')!=-1 /* I don't know, if this concerns also Netscape 6.01. */
navigator.userAgent.indexOf('Netscape6\/6.0')!=-1/* This concerns also Netscape 6.01. */

Because there are different types of Mozilla (for example Mozilla 0.9.1 and Milestone 18), Build ID based detections are more covering. Anyway it is possible to detect Mozilla Gecko browsers as exact as it is necessary.

Netscape browsers can detect indepent from Mozilla browsers by using additional conditions like navigator.vendor == ("Netscape7"). Then you can give different dates for Netscape browsers if it is necessary, for example:

NetscapeGecko = ((navigator.vendor == ('Netscape6') || navigator.vendor == ('Netscape7'));
else if (Mozilla101&&NetscapeGecko)
else if (Mozilla11&&!NetscapeGecko)

There are much reasons to separate Gecko browsers. For example with some 6.1+/ corresponding Mozilla browsers inside position:fixed defined elements position:absolute defined descendants don't strip correctly. The position:fixed defined ancestor creates a container block for position:absolute defined descendant elements, but some builds don't take always correctly account the position of the position:fixed defined ancestor element. In the screen capture with Mozilla 0.9 below position:absolute defined links should be inside the yellow position:fixed defined block (on the base of my tests this matter is fixed at least starting from Netscape 6.2.1).

div.pageGroup, div#allPages, div.allPages2,div#PagesFi, div#PagesEn {position:absolute} /* PagesFi and PagesEn are descendants of allPages */
div[class="pageGroup"], div[id="allPages"], div[class="allPages2"] {position:fixed !important}
div#allPages {left:6px; top:1px;}
div#PagesFi, div#PagesEn {z-index:17; left:2px; top:2px;} /* those Mozilla Gecko 0.9 based browsers, which I have tested calculate the positions of these blocks from the top-left corner of the HTML element ignoring the position of the fixed positioned container DIV, which has allPages as the value of the id attribute */
Mozilla 0.9

In order to get elements into correct position in all modern browsers, it might be necessary to define conditional CSS for Gecko browsers. It should be defined as small quantity as possible. I recommend to read also extra pages, which handle problems of Opera[S] and MS IE[S] browsers.

Also in quite new versions of Netscape/ Mozilla have some problems rendering my dynamic menus in some topic groups (read about problems from a test page[S]).

Such dynamic menus, which have been implemented only by using CSS don't work in Netscape 6.0 (look at models[S]). This is not however a remarkable problem, because dynamic menus are much reasonable to create according to DOM1 JavaScript/ECMAScript + CSS encoding (I handle them closer in another extra page[S]).

The previous mentioned problem relates with the IFRAME element. Many Netscape 6.x/ Mozilla browsers have difficulties with this element (the z-index and positioning don't work correctly). Some versions don't position them correctly. Netscape 6.0 prints them even if they have been defined with display:none. Netscape 6.1+-6.2.1 crash in printing if documents have them and display:none have been used in order to hide these elements. In the newest build of Mozilla has been solved all IFRAME-related problems.

Netscape 6.1+ has fine normal screen presentation. In the fact the only remarkable problem is that it needs more CSS than other modern browsers, because default HTML-settings are not equal with MS IE and Opera. At least following matters should be especially noticed: