Changes to sanitize.css

10.0.0 (June 3, 2019)

These fixes were brought in from normalize.css v10.1.0.

9.0.0 (May 16, 2019)

8.0.1 (May 12, 2019)

8.0.0 (October 8, 2018)

7.0.3 (September 4, 2018)

7.0.2 (September 4, 2018)

7.0.1 (August 25, 2018)

7.0.0 (August 22, 2018)

6.0.0 (June 24, 2018)

5.0.0 (March 1, 2017)

4.1.0 (July 1, 2016)

4.0.0 (June 20, 2016)

Why are variables removed in v4?

Variables were there for developers to override styles in sanitize.css without editing the original file or overriding the rule. However, you should override the rule so that your change is explicit, and so that your source maps accurately indicate your changes coming from your files.

3.3.0 (March 3, 2016)

3.2.0 (February 3, 2016)

3.1.1 (February 1, 2016)

3.1.0 (February 1, 2016)

3.0.0 (October 23, 2015)

2.1.1 (October 5, 2015)

2.1.1 (October 5, 2015)

2.0.0 (September 3, 2015)

1.2.0 (June 16, 2015)

1.1.0 (March 20, 2015)

1.0.0 (11 6, 2012)

Normalize.css had and still has opinionated, developer-centric styles. For example, sub and sup elements are styled to not impact the line height of text, and table, th, and td omit all spacing. As Nicolas pushed Normalize.css into maturity, future preferences like these no longer had a place in the project. Almost a year later, Sanitize was officially branded. Where Normalize.css conservatively follows user agent consensus and results in more pre-styled elements, Sanitize.css liberally follows developer consensus and results in more unstyled elements.

0.0.0 (4 21, 2011)