3 ms·

From my perspective that is not so much a reset/normalize.css but more something like a base.css. A reset.css is supposed to create a common truth across diffe

From my perspective that is not so much a reset/normalize.css but more something like a base.css. A reset.css is supposed to create a common truth across different browsers. However, this doesn't concern so much with different browser default settings but more with developer preference for specific behaviors, like e.g. the boxing model (which is the often being done in a base.css/scss in addition to a reset.css). That is not bad, just the wrong term being used. That being said, I like those settings :-)

notRobot 5y ago
From the article: > A pedantic note > Historically, the main goal of a CSS reset has been to ensure consistency between browsers, and to undo all default styles, creating a blank slate. My CSS reset doesn't really do either of these things. > These days, browsers don't have massive discrepancies when it comes to layout or spacing. By and large, browsers implement the CSS specification faithfully, and things behave as you'd expect. So it isn't as necessary anymore. > I also don't believe it's necessary to strip away all of the browser defaults. I probably do want <em> tags to set font-style: italic, for example! I can always make different design decisions in the individual project styles, but I see no point in stripping away common-sense defaults. > My CSS reset may not fit the classical definition of a “CSS reset”, but I'm taking that creative liberty.
- Waterluvian 5y ago
  But then why call it that?
  - squiggy22 5y ago
    What would you call it? Non-classical-sort-of-css reset.css is a bit long to be fair.
    - JimDabell 5y ago
      Traditionally ,this is called “normalising” CSS. Resetting is to give a blank slate, normalisation is to set opinionated defaults.
unbanned 5y ago
If you read the article you'd see this is addressed
DarkUranium 5y ago
It also runs into this problem, which was mentioned on HN just a few days ago: https://news.ycombinator.com/item?id=29328838 https://news.ycombinator.com/item?id=29328838
- couchand 5y ago
  This article links directly to the one you linked to and explained why it is no longer relevant. I cannot fathom why the sibling has been killed to death, they are objectively correct.

notRobot 5y ago

From the article: > A pedantic note > Historically, the main goal of a CSS reset has been to ensure consistency between browsers, and to undo all default styles, creating a blank slate. My CSS reset doesn't really do either of these things. > These days, browsers don't have massive discrepancies when it comes to layout or spacing. By and large, browsers implement the CSS specification faithfully, and things behave as you'd expect. So it isn't as necessary anymore. > I also don't believe it's necessary to strip away all of the browser defaults. I probably do want <em> tags to set font-style: italic, for example! I can always make different design decisions in the individual project styles, but I see no point in stripping away common-sense defaults. > My CSS reset may not fit the classical definition of a “CSS reset”, but I'm taking that creative liberty.

Waterluvian 5y ago
But then why call it that?
- squiggy22 5y ago
  What would you call it? Non-classical-sort-of-css reset.css is a bit long to be fair.
  - JimDabell 5y ago
    Traditionally ,this is called “normalising” CSS. Resetting is to give a blank slate, normalisation is to set opinionated defaults.

unbanned 5y ago

If you read the article you'd see this is addressed

DarkUranium 5y ago

It also runs into this problem, which was mentioned on HN just a few days ago: https://news.ycombinator.com/item?id=29328838 https://news.ycombinator.com/item?id=29328838

couchand 5y ago
This article links directly to the one you linked to and explained why it is no longer relevant. I cannot fathom why the sibling has been killed to death, they are objectively correct.