- From: Chris Harrelson via GitHub <sysbot+gh@w3.org>
- Date: Wed, 26 Feb 2020 00:24:14 +0000
- To: public-css-archive@w3.org
> As far as I can tell from your use-case description and described behavior, it's the exact opposite. From your description of the use-case, it's for when you're rendering to a PDF or other page-based _screen_ media. In the case you described, all the pages are `size: portrait` already, and thus suitable for immediately printing with no additional work; you use `orientation` to get the supposed-to-be-landscape pages to be shown in landscape _on screen_. When I said "for printed output", I mean that the printing use case. PDF generation is a kind of printing, it's not "view on the web". > My suggested inversion was the "just for printed output" version, where screen/PDF display works correctly by default (by using `size` properly), and then you use `margin-orientation` to rotate how the margins are laid out so they're in a desirable spot when printing. Browsers don't have any distinction between PDF and non-PDF printed output, do they? PDF output is an implementation detail of the user agent outside of the control of the web developer. > If the use-case is ... This is another motivation, yes. However, I don't agree with the notion that this is a hack. The other proposed solutions, as far as I can tell, imply a very large amount of implementation work (even more than just implementing full fragmentation, because there is the proposed additional feature of rotating headers and footers differently than the page layout). Therefore this solution is has positive design points for the (valid, non-hack) use-cases stated. -- GitHub Notification of comment by chrishtr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4491#issuecomment-591161867 using your GitHub account
Received on Wednesday, 26 February 2020 00:24:16 UTC