Quote:
Originally Posted by DNSB
Personally, I tend to use width percentages and height percentages relative to an 600x800 minimum screen resolution so the images appear close to the same size on any of my devices. The samples I've seen in this thread using a max-width expressed in pixels(*). would have my KA1 showing a image less than 50% of the width of the screen while on my old Touch, it would be close to the width and height of the screen (~532x800 for the 626x942 number quoted) if the aspect ratio was maintained.
(*) Pixels like other absolute measurement unit should be banned in ebooks.
|
Agreed. But there are some times when there's no choice. If you're making ebooks for Amazon, you have to state pixel sizes on images that are smaller than the full width of the screen in the fallback media queries for KF7. The KF7s don't obey CSS and % widths. So...fallback is necessary.
Quote:
Originally Posted by slowsmile
@Hitch...The reason you should put the width percentage value in an inline style is specifically to avoid any tinkering of that percentage by -- specifically -- the Kindle overrides in Kindle ebooks. The latter only applies to images in your ebook that are smaller than 100% of the device screen width/height. So if you put your percentage width into an inline style within the image tag(or even in a surrounding div tag) then the Kindle overrides wont be able to find it. Hence no tinkering occurs.
|
Y'know, William, I don't know why you say that this exists. We've never had a single problem with this, and as you know, we make a LOT of books, and a lot of books with images smaller than 100% of the width of the screen. Why do you think that this occurs?
Hitch