"always-unless-keyword" #Įxpect quotes around every font family name that is not a keyword. If you want to use the font family name "Hawaii 5-0" you will need to wrap it in quotes, instead of escaping it as Hawaii \35 -0 or Hawaii\ 5-0. CSS font-weight property defines whether the font should be bold or thick. are not displayed in a particular inbox and you cant edit it in the HTML editor. CSS font-size property sets the size of the font. Fortunately, we can list a family of fonts and the email client will. Quotes should never be used around vendor prefixed system fonts such as -apple-system and BlinkMacSystemFont.įor more on these subtleties, read "Unquoted font family names in CSS", by Mathias Bynens.Ĭaveat: This rule does not currently understand escape sequences such as those described by Mathias. CSS font-family property specifies a prioritized list of one or more font family names and/or generic family names for the selected element.You can probably bet that almost every font family name you use will be a valid CSS identifier. For example, a font family name requires quotes around it if it contains $, ! or /, but does not require quotes just because it contains spaces or a (non-initial) number or underscore. Quotes are required around font-family names when they are not valid CSS identifiers.Quotes are recommended in the spec with "font family names that contain white space, digits, or punctuation characters other than hyphens".(If you actually want to use a font named "sans-serif", turn this rule off.) Therefore, all of the options below enforce no quotes around these keywords. Instead, you use these keywords to point to the built-in, generic fallbacks (right?). will look for a "sans-serif" font) - which is almost never what you want. If you wrap these words in quotes, the browser will not interpret them as keywords, but will instead look for a font by that name (e.g. The font and font-family properties accept a short list of special keywords: inherit, serif, sans-serif, cursive, fantasy, system-ui, and monospace.Please read the following to understand these options: String: "always-where-required"|"always-where-recommended"|"always-unless-keyword"
This rule ignores $sass, and var(-custom-property) variable syntaxes. There seems to be a bug here:Username: