CSS Resets

We will focus on making our layouts look the same in all browsers and speeding up our coding with expandable shortcuts. We’ve covered a large portion of the basics that we need to know to code HTML and CSS websites.

In this chapter, we’ll be dealing with the following two concepts in front-end web development:

• CSS resets
• Emmet

What lead to the appearance of CSS resets

In the early 2000s, there was a period called “browser wars,” when browser vendors did not adhere to the same standards in how web pages were rendered on the screen. While most vendors were following these standards, there were still many who weren’t.

Consequently, the same piece of JavaScript code would break in certain browsers, or produce unexpected results. This resulted in various workarounds, such as browser sniffing—detecting what browser a web page was accessed on so that the web page could be served with conditional code for that browser only. As far as CSS goes, it had its fair share of issues. The biggest problem was that the same CSS code would render completely differently from one browser to the other.