#Inherit google font code
#Inherit google font mac

If you want to learn more about using custom fonts in the slider, check the related article for detailed instructions. You can also use these fields to make your custom font family as the default font when you add a layer, or make them appear in the preset list. Preset font families - These are those font families, which appear in the Preset dropdown list inside the Layer window, so if you would like to change them or add to them, just go ahead, one line is one font (Use ' signs around the font's name if there is a space character in it.).Default family - This is the default font family on every text.While doing some research I really couldn't find any justification for this behaviour in the specs either, not even in the suggestions for rendering HTML documents that you can find for HTML 2, HTML 4 or HTML5.Īs I said, I'm in favor of going back to inherit but let's try to consider as many aspects as we can, so we don't end-up going back and forward with this again. That's why, in this case, I think inherit should't cause unwanted side-effects, since this is how, after all, most elements behave. Arguments like 'this causes less work' or 'the most common thing to do is set a base font' are true, but the most important thing to consider is that form elements don't inherit the font-family property as mostly all other elements do. I don't quite agree that this is a convenience style, -at least not like body. Now I think I was wrong, at least regarding to form elements. At the time made total sense to me: inherit needed to be avoided. When we made this change, we were trying to eliminate the unwanted side-effects of inherit, which in the past has been the reason of many opened issues. I agree, font-family IMO should go back to inherit.

#Inherit google font mac

I’ve read #591 and I want to specifically say I’m only addressing font- family and not offering an opinion on font-size or line-height.ġ As just one example, Mac Chrome sets input to monospace while Mac Firefox sets it to -apple-system and IE 11 sets it to Arial ( fiddle)

#Inherit google font code

Is that a big group? Outside those two conditions being met, everyone else has to write more code to override the new normalize rule. The current rule optimizes for people who 1) Don’t want form elements to use the base font family they assigned and 2) Definitely want the form element font to be sans-serif. If not, I probably have a very specific look for form elements that I’ll have to write code for no matter what. If my site uses Open Sans as its base font I will probably want my form elements to use Open Sans. 1 But I think the normalization should be inherit, not sans-serif.īecause inherit causes less work in the majority of cases. I believe Normalize does have to set something for form elements’ font-family as part of its goals since browsers do set differing default values for that property.

This is a simple technique to achieve consistent site appearance. (Weakly, meaning very easy to override in special cases). I then appreciate that font being (weakly) inherited by every element automatically. I think the opinionated setting of font-family on form elements causes more work in the typical case and is outside the spirit of normalize.cssĪs a user of this library, the most common thing I do is set a base font for a project.