If you've had difficulties getting your web page to display correctly in more than one browser, you're not alone. The unlikely culprit might just be in the Doctype tag that you may or may not have added to your document.
QuirksMode goes into significant depth on the issue: "When Netscape 4 and Explorer 4 implemented CSS, their support did not match the W3C standard (or, indeed, each other). Netscape 4 had horribly broken support. Explorer 4 came far closer to the standard, but didn't implement it with complete correctness either. Although Explorer
{Update: We inferred logic where there was none. The W3C has not changed the behavior of its validation service per the rationale explored below. The service is simply broken. Presumably it will get fixed. Meanwhile, many valid CSS sites will be incorrectly labeled invalid. Don’t start redesigning just yet.}
The W3C’s CSS validation service has changed the way it interprets CSS authoring practices. Many sites that were designed valid no longer validate. The change in behavior affects sites that use the box model hack to compensate for the
Introduction
If you are a web designer or front-end developer, you are probably familiar with how different browsers or user agents displays your code in their own way. Picture this: You are pushing pixels and refining your designs so it fits perfect in your Firefox browser, but when presenting your design to the client in Internet Explorer, your pages might brake completely. Bye bye contract. Designing with CSS is no exception. On the contrary – table based layout seems to be more cross-browser consistent than CSS positioning. This probably one of
RSS/XML