Yes, there's that, plus countless other similar CSS errors, lots of
IE-only CSS extensions like filter:transition(blah), and plenty of JS
sniffs like
if(!isIE) return false;
else //do lots of IE-only non-standard DOM and style manipulation.
I'd send the site author to the W3C site (www.w3.org) and have him read
through the CSS2 spec at the very least, especially the section on
units. Also, if he's brave he can read through the DOM specs. Lastly,
developer.netscape.com has some nice materials on how to do proper
browser detection and how to not leave any browser out of your sniffs.
If after this he still doesn't see how to fix his site, there are plenty
of developers in newsgroups or help sites whom he could ask for help.
If he is serious about becoming a better developer (everybody should
always strive to improve), then he should want to learn how to code
according to the W3C recommendations. Then his work will display in all
standards-compliant browsers, and he'll be able to take advantage of new
powerful W3C technologies as they appear.
--J
> Well, for once, many of his style-declarations are missing units like
> "pt" or "px".
>
> Christian
>
