View Single Post
Old 05-10-2024, 08:42 AM   #15
Quoth
Still reading
Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.Quoth ought to be getting tired of karma fortunes by now.
 
Quoth's Avatar
 
Posts: 14,396
Karma: 107076273
Join Date: Jun 2017
Location: Ireland
Device: All 4 Kinds: epub eink, Kindle, android eink, NxtPaper
Quote:
Originally Posted by DNSB View Post
Evidently, they read somewhere that their ebook would work everywhere because everything supports JS.

Most physical ereaders and many apps don't. There are even web browsers that don't support JS.
Also not all JS makes sense in a ebook even if JS does work.

But you know all this

I do preview on a 4.3″ android and 5″ and 4.7″ eink as well as big screens, in mobi, azw3 and epub. I may stop checking mobi. Only four very ancient Kindles don't support azw3/KF8 and anyone with a non-Kindle only doing mobi (some old phones & PDAs?) likely has Calibre by now, or buying a new ereader.

Width or height for auto mostly works.

An oddity is that on some Kobo FW if an image is specified in pt (using px or % is better), the image does scale with user font selection. 12pt ought to be 1em. 12pt might be 16 px, when at default size. None of that applies to paper and may not apply to browsers. Also 1 px is a logical pixel. It might not be one screen dot.

Last edited by Quoth; 05-10-2024 at 08:52 AM.
Quoth is offline   Reply With Quote