View Single Post
Old 05-09-2024, 04:40 PM   #14
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 46,737
Karma: 169712580
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by theducks View Post
Auto to me is do the other part.
It does not mean preserve.
I specify width and TAKE what auto gives me for height.
But that is for full page images.
Ya gotta help with small images or you might get biggun's
ASSuming the container is large enough, auto comes pretty close to preserve aspect ratio.

If I have images that are vertically oriented, I might go with width: auto; and set the height by percentage. Or I might go for the full sextet of height, max-height, min-height, width, max-width and min-width.

And then there was one abomination where the author used JavaScript so you had image/box sizes that were theoretically sized to the screen dimensions. That was a total CF of an ePub partly due the author not being very familiar with JS and copy/pasting a lot of the code from the web. They were very unhappy when I simplified the code to make the use of JS unnecessary despite the fact that his original ePub caused KDP to generate enough error messages to make them useless for troubleshooting. Evidently, they read somewhere that their ebook would work everywhere because everything supports JS.
DNSB is offline   Reply With Quote