- From: Daniel Holbert via GitHub <sysbot+gh@w3.org>
- Date: Wed, 28 Jun 2023 17:46:22 +0000
- To: public-css-archive@w3.org
> Given that there's prior art for allowing zero-sized page areas on nonzero-sized pages, I'm happy to withdraw the request to add any special cases for those (though that does mean that Chrome at least has some nonconfirming behavior on those & might want to change).
Update: we have actually [encountered one case of a site depending on Chrome's behavior here](https://github.com/webcompat/web-bugs/issues/117996). The site (https://www.theaa.com/ route planner) specifies `@page { size: 16px; }` for some inexplicable reason, when generating printable driving directions. Notably, that's a positive page size, but it's small enough that the page content box (the *page area* that @faceless2 referred to) will be <=0 once the default page margins are subtracted out.
Given this in-the-wild observation of a production site using a bogus 16px page size for intended-to-be-printed-onto-regular-sized-paper content, I'm leaning towards implementing the same graceful-fallback behavior that Chrome seems to have here, for compat & user-benefit. It's not obvious to me that the nonzero-pagesize-but-zero-page-area use-case is important/valid enough to support faithfully, if it creates the potential for this sort of footgun.
--
GitHub Notification of comment by dholbert
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8335#issuecomment-1611837978 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 28 June 2023 17:46:24 UTC