Improve consistency with @csstools/normalize.css

[kripod]

No description provided.

[sindresorhus]

Please fill out the description field when you do pull requests. It's not clear why we should be consistent with a random fork of /~https://github.com/necolas/normalize.css/

[kripod]

Thanks for the fast feedback and sorry for the lack of description. The reason behind forking the original project is explained in the changelog of csstools/normalize.css. It isn't just a random fork, as Jonathan Neal, the original author of normalize.css besides Nicolas Gallagher is behind it:

There are now 2 versions of normalize.css. Nicolas Gallagher and I started
writing normalize.css together. I named and created the normalize.css
repository with the help of Paul Irish and Ben Alman. I transferred the
repository to Necolas, who made it into a “household” CSS library. Much
later I resumed management of normalize.css with Luciano Battagliero. We
tagged, deprecated, and removed “opinionated” styles — styles developers
often prefer but which do not fix bugs or “normalize” browser differences.
Necolas disagreed with this change, and resolved the matter AFAIK by removing
all of the other contributors, locking discussion threads, wiping my name
(and his) from all files, and blocking me from being able to follow the
project.

I may later create a new project with a new name, but for now I intend to
continue working on the normalize.css project, sometimes under the
“csstools” tag. I hope one day our differences are resolved and the projects
will be one again.

For reference within this project:
normalize.css resolves bugs and common browser inconsistencies.
opinionated.css does the same while preserving the classic opinionated styles.

[sindresorhus]

The reason behind forking the original project is explained in the changelog of csstools/normalize.css. It isn't just a random fork, as Jonathan Neal, the original author of normalize.css besides Nicolas Gallagher is behind it:

That should really have been in the readme of that repo.

[kripod]

I totally agree, thanks for the suggestion! I've opened an issue about it for that repo.