\
\Dec 18\\
\
\
\
\- Posted in \\CSS\\\
\- \\\
\\
\
\
\
\By Tim Wright and TJ Kelly\\
\
\CSS\ is the best thing to happen to the web since Tim Berners-Lee. It\'s simple, powerful, and easy to use. But even with all its simplicity, it hides some important capabilities. Ask any designer, and they\'ll tell you that the majority of their code headaches are caused and ultimately solved by CSS.\
\
All designers at some point in their career go through the process of encountering a weird display issue, searching for a resolution, and discovering a trick, technique, or hack could have saved them hours of frustration-\if they had only known when they started.\\
\
We\'ve put together a list of the most frustrating and time-consuming CSS headaches and, more importantly, their solutions (along with examples and further resources). I hope this list will help you save some gray hairs. As for me, I think I feel some coming in right now…\
\
\\\
\
Resets & Browser Inconsistencies\
\
Not all browsers are created equal. In fact, every browser is different. What is the default margin, padding, or font-size of a \\\
element? You might be surprised at the wide range of values. To handle the differences between browsers, many of us want to level the playing field and start from scratch, by using \CSS reset styles\.\
\
The early stages of resets, designers dealt with differing margin and padding values, using a global reset:\
\
\* { margin: 0; padding: 0; }\
\
\
But, as more people used and discussed resets, it became clear that resetting only margin & padding wasn\'t enough (and, applying the above rule to \every element\ is taxing on the rendering engine). Thanks to \