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
(Also make sure your browser is at default zoom and that the sidebar appears.)
The zoom level that the document loads at is lower than it could be. On Chrome/Mac, you could up the zoom by two notches and still contain the entire document image plus the "p. 1" text. On Safari/Mac you could increase by one notch.
Getting the image as large as possible is important for Overview, because the user relies in part on very rapid user scanning of many documents, and we don't have any screen real estate to waste on needless padding.
The text was updated successfully, but these errors were encountered:
The maximum zoom level by default (unless you override it) is the 700px-wide version of the image. Anything larger than that needs to load the 1000px-wide versions of the image. Part of our rationale was not making documents unintentionally comically large. Some folks have big monitors, and the full 1000px zoom can look like old-folks font.
That said, I think you have a good point for many documents with fine print. Let's change the logic to allow the "autozoom" feature even at sizes larger than 700px.
This happens with many documents and browser widths, but for a concrete example: set your browser window width to 1110 (or thereabouts, check in console with window.innerWidth), then go to https://www.documentcloud.org/documents/527670-oregon-zoo-elephant-contract.html
(Also make sure your browser is at default zoom and that the sidebar appears.)
The zoom level that the document loads at is lower than it could be. On Chrome/Mac, you could up the zoom by two notches and still contain the entire document image plus the "p. 1" text. On Safari/Mac you could increase by one notch.
Getting the image as large as possible is important for Overview, because the user relies in part on very rapid user scanning of many documents, and we don't have any screen real estate to waste on needless padding.
The text was updated successfully, but these errors were encountered: