View Single Post
Old 04-13-2022, 09:29 PM   #3
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 46,845
Karma: 169712582
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
It may be valid CSS for a web browser but is it valid CSS in an ePub2 or ePub3 which use subsets of CSS2 and CSS3 respectively. I ran your snippet through the W3C online validator. For Epub3/CSS 3, it commented about the multiple vendor extensions (the -webkit-font-whatver lines), for ePub2/CSS2.1, it not only complained about the vendor extensions but added 3 errors (2 about settings that don't exist in CSS2.1, one that complained about the use of rem which not valid in CSS2.1. You may want to start using ePub3 if you need to make use of those features. OTOH, anyone who uses Times New Roman in an ebook is a hopeless romantic.

Click image for larger version

Name:	W3C_Check_CSS2.png
Views:	145
Size:	94.8 KB
ID:	193219
DNSB is offline   Reply With Quote