Re: [csswg-drafts] [css-page-3] Specify how to handle page sizes with zero area (#8335)

So: closing out the thought, that's why I feel like `size:0` should be treated as `auto` (scenario (1) in my initial comment here).

As for scenario (2), i.e. nonzero page sizes that still produce a 0-size page content box due to large margins:
I can see "whelp, you get a blank page" being more justifiable there (and more possible to print-preview and produce PDF output).  

However, RE your note about wanting to avoid "vastly different behavior at size 0 and size 0.1px" -- there is already a substantial discontinuity there, and it's unavoidable. A small-but-nonzero-sized page content box can still be filled with the page's background-color (for example), and it can even theoretically contain useful text content which can be zoomed-to-be-seen, if the user has their print scale set to "fit page width", as is the default in Firefox at least.  (The output will be an extremely tiny PDF file, but it could contain tiny vector representations of text that can be zoomed in and viewed, at least in theory.)  Whereas for a zero-sized page content box, it's just always blank, and there's no way around that.  So: there's a substantial difference between 0 and 0.1px already.  My suggestion is that we embrace this discontinuity and opt to make the "zero" side of it likely-useful instead of likely-useless.

Also: if we create a special case for 0-sized **pages** being treated as auto (as I think we should for reasons described in previous comment), then it's seems kinda reasonable to take that a small step further and apply the same fallback to zero-sized **page boxes**, for reasons described in this comment.

-- 
GitHub Notification of comment by dholbert
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8335#issuecomment-1399049773 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Friday, 20 January 2023 23:00:08 UTC