The colors of this site are rendered correct in MS IE 4.0+, Opera 3.6x+ and Netscape 6.0+/ corresponding Mozilla browsers. This site works overall best with the newest Opera and Mozilla browsers (details). Also Netscape 6.1+, MS IE 5.5+ for Windows, MS IE 5.0 for Mac and new NeoPlanet browsers render this site quite well. The presentation is poor with Netscape 4.x and it has some clear rendering errors. It doesn't render either advisory titles of some elements and all internal links don't work.

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.

Instructions for CSS tables

Instructions:

* = this feature is different in CSS1 and CSS2.

Background colors in the selector and property
lists are related to the existing HTML, XHTML or
CSS specifications like in HTML-tables (the coloring of HTML tables ([S])). In
browser columns it concerns also the functionality of the
CSS. I explain below the meaning of used colors.

Standard

Concerning the selector or property
list, the selector/rule belongs to HTML 4.01, CSS1 or CSS2
specification. Concerning browsers support green means relative
good implementation. Note that it doesn't necessary mean bug free
implementation but just so much working implementation, that the
property/rule can be used without big problems.

Proprietary or buggy

Gray background means proprietary
and/or problematic implementation.

Future

Lime means that they are questionable
to support, because they are working drafts (WD) for future XHTML or CSS3
specifications. Note. A WD can at some level regard as a part of future specification, because it is accepted to evaluate as a future specification or a part of future specification. The problem is that WD can change. Some not recently edited Working Drafts are however rather just proposals. A proposal is not necessary a part of future specification - it is just a matter, which under public discussion if it could be accepted as a new specification/ a part of a new specification.

Old

Because these elements don't belong to modern specifications, it is questionable to use them.

Questionable

I have not tested the rule/property
or I'm not sure, if the feature is implemented. The implementation might be totally proprietary.

Tapio Markula 1999-2001 (@dnainternet.net) - not into the public use without the permission (add to beginning of the e-mailaddress my name, Tapio Markula, separated with a comma).