What is the difference between a CSS reset and Normalize.css, and when should you use each?

What is the difference between a CSS reset and Normalize.css, and when should you use each?

• A. Reset removes defaults entirely; Normalize preserves sensible defaults and cross-browser consistency; Normalize is often preferred for a practical baseline.
• B. Reset preserves defaults; Normalize resets them.
• C. They are the same and can be used interchangeably.
• D. Reset removes defaults entirely; Normalize.css preserves sensible defaults and cross-browser consistency; Normalize is often preferred for a practical baseline.

Answer: (D)

The main idea here is how aggressively you handle browser defaults. A CSS reset wipes out most of the browser’s built‑in styles so you start from a clean slate, removing margins, padding, borders, typography, and other defaults across elements. Normalize.css, however, doesn’t erase those defaults; it preserves sensible defaults and fixes cross‑browser inconsistencies so the baseline looks the same in different environments while keeping predictable, usable defaults intact. That’s why the best approach is to rely on Normalize.css for a practical baseline. It gives you a consistent starting point with fewer surprises, while preserving browser behaviors that users expect. A full reset can be useful only if you want total control from the ground up and are prepared to re‑style most elements, which tends to add more work and can impact accessibility if you remove useful defaults. In practice, Normalize.css is often preferred, with optional, small reset tweaks applied only where you need them.

The main idea here is how aggressively you handle browser defaults. A CSS reset wipes out most of the browser’s built‑in styles so you start from a clean slate, removing margins, padding, borders, typography, and other defaults across elements. Normalize.css, however, doesn’t erase those defaults; it preserves sensible defaults and fixes cross‑browser inconsistencies so the baseline looks the same in different environments while keeping predictable, usable defaults intact.

That’s why the best approach is to rely on Normalize.css for a practical baseline. It gives you a consistent starting point with fewer surprises, while preserving browser behaviors that users expect. A full reset can be useful only if you want total control from the ground up and are prepared to re‑style most elements, which tends to add more work and can impact accessibility if you remove useful defaults. In practice, Normalize.css is often preferred, with optional, small reset tweaks applied only where you need them.