View Single Post
Old 07-25-2021, 02:49 AM   #9
Jellby
frumious Bandersnatch
Jellby ought to be getting tired of karma fortunes by now.Jellby ought to be getting tired of karma fortunes by now.Jellby ought to be getting tired of karma fortunes by now.Jellby ought to be getting tired of karma fortunes by now.Jellby ought to be getting tired of karma fortunes by now.Jellby ought to be getting tired of karma fortunes by now.Jellby ought to be getting tired of karma fortunes by now.Jellby ought to be getting tired of karma fortunes by now.Jellby ought to be getting tired of karma fortunes by now.Jellby ought to be getting tired of karma fortunes by now.Jellby ought to be getting tired of karma fortunes by now.
 
Jellby's Avatar
 
Posts: 7,561
Karma: 20150435
Join Date: Jan 2008
Location: Spaniard in Sweden
Device: Cybook Orizon, Kobo Aura
Quote:
Originally Posted by hobnail View Post
If it's the @supports at the end of your css file that's causing the problem I'd just use the font-variant stuff without checking. I don't know if anything goes wrong if the font doesn't support them.
@supports doesn't query the font, it queries the renderer, i.e., it queries support for the font-variant-numeric property in this case. And in that case I think the @support rule is unnecessary, because a renderer that doesn't support the requested property should just ignore it (except if it's RMSDK, which chokes on unknown stuff, but if it turns out to choke on @supports too, then nothing is gained either way).
Jellby is offline   Reply With Quote