I have a new theory about Netscape: When they realeased Communicator, with supposed partial CSS support, their real plan was to kill CSS from ever being adopted by anyone. They did a very good job of this by screwing up the implementation so badly that it is fricken maddening to try and use. Their motive is unclear, but the evidence lies in the fact that it'd be one thing if they just didn't support some things, but when you try and use CSS in a perfectly proper manner, which works fine on a more compliant browser and it so completely screws things up in Netscape so as to be bewilderingly difficult to figure out what the problem is...well, that's just a whole 'nother level of evil.

Okay, phew. I feel better now.