293541
There are tons of little secrets that one learns along the line when using CSS and XSLT for cross browser support. Of course, the first of these little lessons is NOT to attempt to support too many browsers (or versions of browsers). Current site statistics (random sampling of .com, .net, and .edu) show that the vast majority of folks on the web now use M$ Internet Explorer (IE) 5.5 or newer (over 90%).
In regards to points verses pixels, my suggestion is to always use points. This accomplishes a few things, including putting Netscape users in a very close appearance to the IE users since Netscape has chosen another display method. Furthermore, the point sizes are a closer relative to the print versions and tend to present a better-printed version.
Oh, and many times, the CSS validators out there go too far back in their versioning schema, thus producing errors that are probably not valid with the current browsers. Just a suggestion, but you might want to take a good look at TopStyle Pro for your CSS management and cleanup.
In regards to points verses pixels, my suggestion is to always use points. This accomplishes a few things, including putting Netscape users in a very close appearance to the IE users since Netscape has chosen another display method. Furthermore, the point sizes are a closer relative to the print versions and tend to present a better-printed version.
Oh, and many times, the CSS validators out there go too far back in their versioning schema, thus producing errors that are probably not valid with the current browsers. Just a suggestion, but you might want to take a good look at TopStyle Pro for your CSS management and cleanup.
