Crashers are always bad. Yes, it's Netscape 4's fault, but the page author can still take some responsibility. On the bright side, there are ways of hiding CSS declarations from Netscape 4 and its ilk.

If you specifiy a main stylesheet with a minimum set (if any) of CSS declarations and also include

@import "fullSupport.css";

with all of your declarations including the ones that would normally kill NS4, everyone wins. Netscape 4 doesn't understand the @import directive and so would only see what's in the stub CSS file. Netscape 4, while looking suboptimal (hardly news with the web today), will still be usable for gathering information, and standards-compliant browsers will still look good.

Best of all worlds: Netscape 4 doesn't crash, Netscape doesn't look as good as a recent browser (encouraging upgrades), no one has to avoid any useful CSS idioms, and recent browsers never notice anything hackish.

Sound good?



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to