- From: Daniel Holbert via GitHub <noreply@w3.org>
- Date: Mon, 07 Jul 2025 21:11:39 +0000
- To: public-css-archive@w3.org
> Not sure about `minimum` vs `balanced`. Since we have no control over what the printer does regarding rotating the output, and whether it's the short or the long edge that's fed first, there's no meaningful individual safe inset. Yeah, I don't know for sure if we need those exact keyword values -- I'm just providing a handful of values as examples that might be useful. The idea with `minimum` would be to just use **whatever "safe" margin-values that today's browsers already use** when a user prints a simple web page and chooses "Margins: Minimum" in the print dialog. (This option is available in both Firefox and Chrome at least, and it uses the "safe margins" that we get from the printer.) If these safe-values end up being wrong in certain cases (e.g. due to the printer feeding half of the pages in reverse for duplex printing), then that's presumably already a problem that any software printing with "Margins: Minimum" would be encountering, and I don't see a reason to shield CSS from that problem in this sort-of-edge-case. And if print drivers are (or become) expressive enough to communicate this sort of situation to browsers, then we can account for it when honoring `enforce-safe-margins: minimum` (e.g. swapping the top/bottom safe-margin clamps that we use, on alternating pages). -- GitHub Notification of comment by dholbert Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11395#issuecomment-3046533934 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 7 July 2025 21:11:40 UTC