If every browser on market would 100% comply to the standards set by the World Wide Web Community, the web-designers and developers would have to write only one single version of HTML and CSS code for all the browsers. But because of the great variety of browsers on market and because every browser complies differently to the standards, the developer must search for a way to make his code work on every browser.
The developer is able to use a great range of hacks that assure the compatibility between the browser standards and the used
"In an ideal world we'd write our (X)HTML and CSS once and it would work perfectly for all browsers. In the real world different browsers and platforms render our creations slightly or drastically different, depending on how adventurous we get with our (X)HTML and CSS. To combat these browser peculiarities developers have adopted a number of coping strategies, including:
@import to hide more advanced styles from older browsers (Netscape 4.x etc.)
CSS hacks (voice-family, escapes, "Tantek hacks," and other techniques)
Conditional CSS
While 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