Is this repository maintained at all? #880
Comments
|
@FrankConijn I'd say, it's rather not. Unfortunately, the repo is also a regular victim of strange PRs and issues being raised. Which I guess demotivates the maintainers too. |
|
Are there any alternatives that are better maintained? |
|
I created "norm.css" and "base.css" that I keep updated. norm.css: just crossbrowser normalisation, no opinionated styles. base.css: usefull defaults: I would appreciate a little more community. Also listed under "resources", many different similar projects that I have found. |
|
There is a very similiar issue that was closed by Normalize's author just yesterday. Unfortunately, he did not leave any comment at all. Not sure what to make of that. @necolas Can you please comment on this project's state? I maintain a list of CSS frameworks and consider to drop Normalize.css due to your lack of response.
@curtisbarnard You may find some here: https://github.com/troxler/awesome-css-frameworks/#base--reset--normalize |
I like using the modern-normalize alternative, especially since older browser support is fading. |
Reduces file size (uncompressed) from 8KB to 6KB. The main difference really is dropping all the lte IE 9 support hacks. (https://github.com/necolas/normalize.css/blob/master/CHANGELOG.md) v5 was released way back in 2016 and v8 was released way back in 2018. The repo doesn't seem be maintained and questions asked by the community seem to support that assumption (necolas/normalize.css#880) Theres a bigger question of whether this is the approach we still want to use or perhaps investigate whether there is a modern normalizer out there some where. In the issue I linked to there are a couple of suggestions at alternative ones that we could look at.
Reduces file size (uncompressed) from 8KB to 6KB. The main difference really is dropping all the lte IE 9 support hacks. (https://github.com/necolas/normalize.css/blob/master/CHANGELOG.md) v5 was released way back in 2016 and v8 was released way back in 2018. The repo doesn't seem be maintained and questions asked by the community seem to support that assumption (necolas/normalize.css#880) Theres a bigger question of whether this is the approach we still want to use or perhaps investigate whether there is a modern normalizer out there some where. In the issue I linked to there are a couple of suggestions at alternative ones that we could look at.
|
Since in this issue 2 alternatives were already mentioned, I don't know which one to choose. So I registered https://github.com/NormalizeCSS with the idea that perhaps we can make this a collaborative effort. I'm curious to know what you all think about that. And yes, insert the obligatory XKCD here. |
I see that the last version of the main CSS file dates back 4 years, while numerous issues have been filed since then. And in the meantime, IE has been declared dead by MS, while Edge has switched to the Chromium engine. But the said file reflects none of that. So, is this repository maintained at all?
The text was updated successfully, but these errors were encountered: