> It should be obvious to say that if—or once—all user agents handle CSS the same way, there’s no need for a CSS reset.
I think I disagree, for one, browsers default is not what we expect, a few weeks ago I forgot to put `<meta name="viewport" content="width=device-width, initial-scale=1.0">` in the head tag of a website I was building and nearly lost it. A CSS reset isn't just to standardize browsers, it's to make building on the web in this decade usable. Chrome, Firefox, or whatever you're using is never going to change it's default style sheet because we want it to, they are always going to prioritize the default behavior of the web. The web is so unfathomably old, and browsers will always aim to keep the way the web works the same. A CSS reset, while not strictly necessary to write websites, will reduce the amount of hair pulling you must endure to do it.
> It should be obvious to say that if—or once—all user agents handle CSS the same way, there’s no need for a CSS reset.
I think I disagree, for one, browsers default is not what we expect, a few weeks ago I forgot to put `<meta name="viewport" content="width=device-width, initial-scale=1.0">` in the head tag of a website I was building and nearly lost it. A CSS reset isn't just to standardize browsers, it's to make building on the web in this decade usable. Chrome, Firefox, or whatever you're using is never going to change it's default style sheet because we want it to, they are always going to prioritize the default behavior of the web. The web is so unfathomably old, and browsers will always aim to keep the way the web works the same. A CSS reset, while not strictly necessary to write websites, will reduce the amount of hair pulling you must endure to do it.