Quote:
Originally Posted by Quoth
There is NO ereader that does all the CSS & HTML a website + browser can do.
|
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.