Update normalize.css

[WebVPF]

Current version in materialize v7.0.0 https://github.com/materializecss/materialize/blob/v1-dev/sass/components/_normalize.scss

The author has the latest version 8.0.1 https://github.com/necolas/normalize.css/releases

Latest version file: https://github.com/necolas/normalize.css/blob/master/normalize.css

[ChildishGiant]

The better move would be using the npm package over just having it locally. We might want to look into changing to another package anyway: necolas/normalize.css#856 (comment)

[LoganTann]

The better move would be using the npm package over just having it locally. We might want to look into changing to another package anyway: necolas/normalize.css#856 (comment)

what are your thought about switching to modern-normalize (as suggested in necolas/normalize.css#856 (comment)) for 1.2.0 @materializecss/members ?
It's normalize, but improved and used by tailwind.

[DanielRuf]

what are your thought about switching to modern-normalize (as suggested in necolas/normalize.css#856 (comment)) for 1.2.0 @materializecss/members ?
It's normalize, but improved and used by tailwind.

Generally a good idea, but since we plan v2 after v1.1 (https://github.com/materializecss/materialize/releases) we can do it there. This will include upgrade of all relevant parts.

We already have a v2-dev branch which will become the new default branch then.

[RamonvdW]

Hi, How to assess if it is backwards compatible? Ramon From: Daniel Ruf ***@***.***> Sent: dinsdag 12 oktober 2021 12:07 To: materializecss/materialize ***@***.***> Cc: Ramon ***@***.***>; Team mention ***@***.***> Subject: Re: [materializecss/materialize] Update normalize.css (#137) what are your thought about switching to modern-normalize <https://github.com/sindresorhus/modern-normalize> (as suggested in necolas/normalize.css#856 (comment) <necolas/normalize.css#856 (comment)> ) for 1.2.0 @materializecss/members <https://github.com/orgs/materializecss/teams/members> ? It's normalize, but improved and used by tailwind. Generally a good idea, but since we plan v2 after v1.1 (https://github.com/materializecss/materialize/releases) we can do it there. This will include upgrade of all relevant parts. We already have a v2-dev branch which will become the new default branch then. — You are receiving this because you are on a team that was mentioned. Reply to this email directly, view it on GitHub <#137 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMBUZHQSDIJNMXDD6XGG4KTUGQCEJANCNFSM44UHSW7Q> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub> .

[LoganTann]

How to assess if it is backwards compatible?

Hi @RamonvdW,
a normalizer is a small CSS file that overrides default styling of elements (which are different across browsers) in order to provide a better cross-browser consistency.
If the unit tests are well written and passes correctly, we can assume that switching to modern-normalize is indeed backward compatible.

[RamonvdW]

Hi, I am aware what the normalize module is for. The risks I consider is is the looks of "a site" built on top of MaterializeCSS. I have given it some thought and anything changed in normalize that are "pass through" for MaterializeCSS (thus possibly affecting "the site") simply have to be found by the testing of "the site" itself. You have my support to change it! Ramon

…

On Sat, Oct 16, 2021 at 12:19 PM ShinProg (Logan Tann) < ***@***.***> wrote: How to assess if it is backwards compatible? Hi @RamonvdW <https://github.com/RamonvdW>, a normalizer is a small CSS file that overrides default styling of elements (which are different across browsers) in order to provide a better cross-browser consistency. If the unit tests are well written and passes correctly, we can assume that switching to modern-normalize is indeed backward compatible. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#137 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMBUZHUHVIN5VYFRYS5Q363UHFGRXANCNFSM44UHSW7Q> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.