Normalize.css: Why set font family?
Why did you do this? This added a headache! I have a custom font in the project and I had to redistribute the entire block ... It's not cool!
Sky161
All 6 comments
Agreed, this is not necessary. Why just not to make Class with family standard and just implement it on body page.
Fargard
on 18 Aug 2017
You have to set font-family for inputs in any case, font-family for <body> doesn't affect inputs.
You could look at http://www.cssdesk.com/V2Zam that proves it.
I tested it on Firefox 55.0 and Chromium 59.0.3071.104.
unclechu
on 18 Aug 2017
@unclechu true, but why define sans-serif instead of this?
input {
font-family: inherit;
}
before this change you could define font-family on html/body and be done with it. Now you'd have to define it for more (which exactly?) elements.
oskarrough
on 6 Sep 2017
@oskarrough
you could define font-family on html/body and be done with it
No you couldn't. This is my point.
unclechu
on 6 Sep 2017
@unclechu but if we use inherit instead of sans-serif as @oskarrough suggested we would not have to do redeclare later on in our project.
Example: https://jsfiddle.net/9vcdta90/
hatzipanis
on 8 Sep 2017
It's now inherit
necolas
on 9 Feb 2018
Related issues
visicode
路
5Comments
henrik
路
7Comments
ghost
路
6Comments
ShaggyDude
路
7Comments
denis-sokolov
路
4Comments
Most helpful comment
@unclechu true, but why define
sans-serifinstead of this?before this change you could define font-family on html/body and be done with it. Now you'd have to define it for more (which exactly?) elements.