View Single Post
Old 04-08-2024, 05:44 AM   #9
JSWolf
Resident Curmudgeon
JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.JSWolf ought to be getting tired of karma fortunes by now.
 
JSWolf's Avatar
 
Posts: 74,346
Karma: 129333690
Join Date: Nov 2006
Location: Roslindale, Massachusetts
Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3
Quote:
Originally Posted by Turtle91 View Post
You, of course, can continue to use the pseudo-elements, they just might not work. Assuming the Kobo is standards-compliant it will just not render with the pseudo-element css. It should just ignore that coding completely. You can, and should, set your css so that your book still looks acceptable if there is any coding that gets ignored.

If a device doesn't follow the standards then submit a complaint/bug report so they can get it fixed.
The only way for Kobo to fix RMSDK to allow pseudo elements is for Kobo to update RMSDK to the latest version and I cannot see that happening.

If this is an eBook for sale or to be read as ePub on a Kobo, then pseudo elements cannot be. A <span> will have to be used instead.
JSWolf is offline   Reply With Quote