footer text on small screen get pushed up into main body text

[hank-pim]

Steps to reproduce

I seen on a few epubs ive been reading. Where the footer text gets pushed up due to length and can overlap with the book text. I'm guessing its because my eink reader has a small narrow display.

Expected behavior

pushes body up, or text shrinks to fit. Option to adjust top and bottom margins would also probably work.

Actual behavior

Logs

No response

Komga version

1.11.1

Operating system

Linux komga-794d964598-qjgrc 6.1.74-production+truenas GNU/Linux

Installation method

Docker

Other details

No response

Acknowledgements

• I have searched the existing issues (open AND closed) and this is a new ticket, NOT a duplicate or related to another open issue.
• I have written a short but informative title.
• I have checked the FAQ.
• I have updated the app to the latest version.
• I will fill out all of the requested information in this form.

[Benjamin-Watson0]

That's because the address bar occupies space on the screen.
In the Android version of the Edge browser, sliding the screen upwards until the address bar disappears can improve the aforementioned issue.

[hank-pim]

Sorry i should have added this to the description those are full screenshots no cropping. I was using komga in app mode. On android in chrome that's were you click on "Add to Home Screen" when you use that link you get a full screen no ui view of the website. There was no address bar.

If I replicate the screen size using chrome dev tools I can see the same thing.

[Benjamin-Watson0]

On android in chrome that's were you click on "Add to Home Screen" when you use that link you get a full screen no ui view of the website. There was no address bar.

I apologize for the confusion; I thought it was only happening on the web version. Coincidentally, as I was reading, I also added the web page to the screen for use and encountered the same problem.

Based on my experience, the issue seems to be due to an excessive amount of text on that particular page. I haven't encountered this problem on every page.

I look forward to the developers addressing this issue.😊

[github-actions]

🎉 This issue has been resolved in 1.11.3 (Release Notes)