Quote:
Originally Posted by JSWolf
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.
|
That may, or may not, be the case. If Kobo chooses to produce devices that don't support standard CSS then that is a marketing decision and they will reap the results of a substandard product. Letting them know, through bug reports, that the customer isn't happy is a sure fire way they will get the message.
All of that does not change what I said. You should always design your css to include fallback coding so that it still looks acceptable.