- From: Daniel Holbert via GitHub <sysbot+gh@w3.org>
- Date: Tue, 28 Feb 2023 20:40:32 +0000
- To: public-css-archive@w3.org
dholbert has just created a new issue for https://github.com/w3c/csswg-drafts:
== [css-page-3] Specify how to handle negative page margins ==
(Related to https://github.com/w3c/csswg-drafts/issues/8335 , but now for margin...)
I don't think the css-page-3 spec ( https://w3c.github.io/csswg-drafts/css-page-3/ ) defines what to do (if anything) with negative `@page { margin: ...} ` values (though I may have overlooked it).
In practice:
* Chromium seems to honor negative `@page` margins, effectively inflating the page content area beyond the bounds of the sheet of paper on the sides that have negative margins. (So, content gets clipped on those sides, generally.)
* Firefox clamps negative `@page` margin to 0 (or rather, to the printer's writable page area) with the intent of keeping page content on the sheet. (as of https://bugzilla.mozilla.org/show_bug.cgi?id=1665001 )
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8508 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 28 February 2023 20:40:34 UTC