You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I view this page on IE (IE 11) the cover image is scaled so that the entire image appears on the page; When I view the page on Chrome and Firefox, the image is much larger and only the top portion of the cover is visible.
I'm not sure if this is a readium issue, or if this is an issue with the way the document's markup is constructed; but since the behavior is different between browsers, I thought at least I'd post the issue.
The text was updated successfully, but these errors were encountered:
Update:
On IE, the complete image is scaled to fit the screen.
On Firefox, the image is scaled to take up the entire width of the screen; the image is cut off at the bottom (only the top portion of the image is displayed) and when you move to the next page, readium advances to the next chapter.
On Chrome, the image is scaled to take up the entire width of the screen, like Firefox; when you move to the next page, you see the middle section of the title page image; moving to the next page shows the bottom portion of the title page image; and then you finally move to the following chapter.
The wrapping div (the first child of the tag does not have a sizing css property. If I manually add "height: 100%" then the cover image scales correctly on all browsers I've tested.
Of course, this breaks pages other than the cover, but it's a start.
I have a book with the following markup for the cover page:
When I view this page on IE (IE 11) the cover image is scaled so that the entire image appears on the page; When I view the page on Chrome and Firefox, the image is much larger and only the top portion of the cover is visible.
I'm not sure if this is a readium issue, or if this is an issue with the way the document's markup is constructed; but since the behavior is different between browsers, I thought at least I'd post the issue.
The text was updated successfully, but these errors were encountered: