IMO, being able to specify individual fonts in CSS is a mistake. A competent web designer/developer should be able to manage with generic font families.
That's a fair point, but speaking as a web developer who sometimes gets stuck wearing the designer hat I don't think specifying particular fonts is the answer to nobody having good fonts for the <fantasy> family. Chances are the fonts I specify for <fantasy> text won't be installed on most machines, either; should I inflict an extra megabyte or two of font downloads on people just so my site looks just right?
The end doesn't justify the means.
I didn't think you yourself were, and I'm sorry if I implied otherwise. I was speaking toward a general tendency in webshit to insist on a particular font even if it means having to download that shit from Google or Adobe.
I've been sticking with serif, sans-serif, and monospace because I haven't found a use for the other families, but if I want to use fantasy on my own site I will. If that renders as "Impact" on the client, that's /their/ problem, not mine. :)
Welcome to Ten Forward, a Star Trek themed Mastodon instance! For more information on what Ten Forward is in the Star Trek universe, please read this page on Memory-Alpha. The instance is not restricted to Star Trek role-play or characters. More general purpose use is welcome.