- From: Morten Stenshorne via GitHub <sysbot+gh@w3.org>
- Date: Tue, 21 Jan 2025 10:57:21 +0000
- To: public-css-archive@w3.org
> I guess in that case you could get zero (and the browser would just position / lay out things accounting for the unprintable margin). Thanks for mentioning this! Yes, that's my thinking as well. If there are multiple pages per sheet surface, the author no longer has any control over the sheet, so the browser should report nothing unprintable to the document, and just apply whatever margin it wants at the actual sheet edges, depending on user settings, maybe? It doesn't make a whole lot of sense to honor specified page margins at sheet edges when there are multiple pages there, although Chrome currently does that, actually. > > This means that authors have no means of confidently setting page margins to prevent content (inside a page margin box, or even inside the page area) from getting clipped. > > Firefox at least has a mechanism to ensure the page margins are at least the unprintable margin (unwriteable in Gecko terminology) [here](https://searchfox.org/mozilla-central/rev/345ec3c55ddda5f0ce37168f0644dcdcc4834409/layout/base/nsPresContext.cpp#2193-2201), so I haven't seen that come up too much in practice, fwiw. That setting can be used to avoid clipping in the page area, but not in the page margin boxes, right? -- GitHub Notification of comment by mstensho Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11395#issuecomment-2604394580 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 21 January 2025 10:57:22 UTC