css - Are font classes defined by client os or client browser? -
i have noticed @ google fonts never use fantasy fallback class in font-family. script , typical fantasy fonts, use cursive.
i wonder if hint chrome not support fantasy fallback class? case, fallback font-classes have handled browser via implemented lists typical serif, sans-serif etc. fonts. alternatively, browser query os such lists?
what happens when browser needs fallback serif font on clients system? how info on installed serif fonts?
i haven't been able find aswer this, hope here might know it. know web safe fonts , become things of past, still have relevance.
typefaces don't map generic font families mechanically. they're categorized way in family names , on font listings such google fonts , adobe typekit.
you create font stack consists of sans-serif family, serif family, , ends fantasy
keyword:
font-family: helvetica, 'times new roman', fantasy;
and browsers treat same: use whichever family comes first supported, or fall generic family if comes that.
i expect browsers implement @ least 5 generic families defined in css2.1 , css-fonts-3: serif, sans-serif, cursive, fantasy, , monospace. which faces each generic family maps less predictable — one, browsers offer user ability change preferred default serif, sans-serif , monospace families. , then, entire list of installed fonts available selection in every category, suggests browsers can't (or @ least don't) differentiate between categories of fonts.
the default preferences browser ships based on assumptions of fonts preinstalled on given system.
i can't answer why google fonts doesn't seem specify fantasy in of font stacks.
Comments
Post a Comment