View Single Post
Old 08-29-2023, 02:21 PM   #111
theducks
Well trained by Cats
theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.
 
theducks's Avatar
 
Posts: 31,139
Karma: 60406498
Join Date: Aug 2009
Location: The Central Coast of California
Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A
Quote:
Originally Posted by nabsltd View Post
I'm not expecting that, but I do expect that a current release eReader will support CSS that was supported 10 years ago by every browser. If an current-release eReader uses webkit or other rendering framework as its base, there is no excuse for completely ignoring CSS properties that have been supported by that framework for over 5 years.

In other words, it's actually harder to disable support for CSS properties than to just let the framework do what it was written to do. I understand tossing out HTML and CSS support that has little use in an eReader (forms, scripting, etc.), but basic formatting that has been solved for many years makes little sense.
EPUB is a subset. Browser do full motion (animation). e-ink (a common display) does not or just barely) ipdf.org is the site to read about e-book formats
theducks is offline   Reply With Quote