View Single Post
Old 06-14-2025, 02:47 PM   #36
ElMiko
Evangelist
ElMiko has read every ebook posted at MobileReadElMiko has read every ebook posted at MobileReadElMiko has read every ebook posted at MobileReadElMiko has read every ebook posted at MobileReadElMiko has read every ebook posted at MobileReadElMiko has read every ebook posted at MobileReadElMiko has read every ebook posted at MobileReadElMiko has read every ebook posted at MobileReadElMiko has read every ebook posted at MobileReadElMiko has read every ebook posted at MobileReadElMiko has read every ebook posted at MobileRead
 
ElMiko's Avatar
 
Posts: 480
Karma: 65460
Join Date: Jun 2011
Device: Kindle
Yeah, RbnJrg, I see we're kind of talking past each other, and I apologize for that. As I mentioned before, I have no doubt that the svg solutions you've proposed would pre-empt the problems of a non-svg approach. The nature of my question in post #33 wasn't really about HOW to get a full screen, proportional image (a problem for which you've already provided extremely thorough responses), but rather a questions about WHY the non-svg approach was behaving in the way that it did.

So, for example, while you have a solution to fitting the image on a single page (by reducing the height to 99%, which is what I had done and adding a contingent vh specification), I'm puzzled by why 100% height would produce greater than 100% height in the non-svg example, despite having set the html, body, and container to 100% as per the Josh Comeau article.

Likewise, I understand that an SVG wrapper would preempt the variously scrolling/squeezing issues, but don't understand why Sigil treats it one way and Calibre treats it another.

Last edited by ElMiko; 06-14-2025 at 02:53 PM.
ElMiko is offline   Reply With Quote