The rendering in epub2 (.epub) is fine.
The rendering in epub3 (.kepub.epub) is not, when the image is to large to fit on current page, with two issues:
top border is displayed where the image would start on page N (image being correctly moved to page N+1)
the area below that border is clickable and follows the link, although nothing is displayed at that location
I realise that having images right next to a screen border is probably not a good idea because it conflicts with tap-screen-to-turn-page UI, but I thought I should report these bugs.
Link-related issue: the page those images link to are full-screen version of the illustrations, with a link over the whole image bringing user back to the (only) page the image appears in. Because the link is then fullscreen, reader UI cannot be triggered. Is it just bad practice, or should the reader software provide some way to trigger its UI rather than pass the event to the page ? (I'm thinking of a long press for example)
In the ebook I'm playing with I use the following construct to display images in text:
CSS:
The rendering in epub2 (.epub) is fine. The rendering in epub3 (.kepub.epub) is not, when the image is to large to fit on current page, with two issues:
I realise that having images right next to a screen border is probably not a good idea because it conflicts with tap-screen-to-turn-page UI, but I thought I should report these bugs.
Link-related issue: the page those images link to are full-screen version of the illustrations, with a link over the whole image bringing user back to the (only) page the image appears in. Because the link is then fullscreen, reader UI cannot be triggered. Is it just bad practice, or should the reader software provide some way to trigger its UI rather than pass the event to the page ? (I'm thinking of a long press for example)