- Shipped
- August 14, 2026 at 6:04 PM UTC
- Author
- kamo
- Commit
- 95ffd81
The percentage reset to one baseline: the page grown to the pane but capped at 920px, which on a wide monitor leaves the sheet floating in a lot of empty desk. That cap is deliberate — a letter page stretched across a 34-inch display is a worse document, not a bigger one, because the eye cannot track a line that long — but it is not always what the member wants. Reading fine print or working a dense form, they want the space they have. So there are now two, and a toggle in the capsule picks which: page the readable width, capped at 920. What the pane opens at. width fills the pane, less a 24px gutter so the sheet's shadow is not clipped against the edge and the page reads as laid down rather than cropped. They are a MODE, not two more stops on the zoom ladder, because they are different intents rather than different magnifications. Zoom multiplies whichever baseline is active, so the readout stays honest about the one it is a multiple of, and + / − still work from either. Switching baseline LANDS on it — zoom returns to 100%. "Fit to width" that left a 250% zoom applied on top would not fit anything, and the member asked for a width, not a multiplier of one. The toggle is one button with `aria-pressed`, and its tooltip names WHAT PRESSING IT DOES rather than what is currently on: "Fit to Width" in page mode, "Reset view" in width mode. Both keys already existed and are non-empty in all 22 locales. maxPageWidthFor covers the edges in tests: a NaN pane measurement falls back to the readable cap rather than reaching PdfPages as maxPageWidth and rendering nothing, and a collapsed pane never returns a width too small to read. One test pins the fact that on a pane narrower than the cap the two modes converge to within the gutter — that is correct rather than a bug to design around.