For normalize.css, following Firefox (and probably future Safari) is obvious to me. For sanitize.css, I could see the backwards argument. Another argument against doing this, though, is undoing Firefox’s choice, which only further hurts adoption of text-decoration styles.
To me, the big difference between normalize and sanitize is that the former takes a "dumb" approach (not in the bad sense of the term) so it's easier to pick a style, with sanitize, there is much more than should be taken into consideration
I was following up on your ask about https://github.com/10up/sanitize.css/blob/release/4.0.0/lib/sanitize.css
so it was about sanitize :)
Actually, generally I'm against opinionated rules in normalize and for very opinionated rules in sanitize
Because in my opinion, they have very different purpose
and it would be bad to see one trying to emulate what the other is supposed to do
@jonathantneal what about https://github.com/10up/sanitize.css/blob/release/4.0.0/lib/sanitize.css#L529 ?
Did things change regarding
[aria-hidden="false"]? Because it was ignored before
That's why I mentioned those last rules
As I'm not sure they have any value
I'll try a few things using your test page
What a step backward :(
@jonathantneal My apologies for not following up earlier. Here's the gist describing the webpack 2 changes https://gist.github.com/sokra/27b24881210b56bbaff7
Er sorry for the inline as well
Thanks all for the great contirbutions to normalize.css v4. If you have a minute, I’m looking for full-time opportunities, and I sure would appreciate a shout out or a retweet. https://twitter.com/jon_neal/status/745672465708265475
Ohh sorry
