- From: Bernhard Fey via GitHub <sysbot+gh@w3.org>
- Date: Mon, 21 Oct 2019 15:58:19 +0000
- To: public-css-archive@w3.org
I am with RealObjects. If we may weigh in on the actual usage of CSS Paged Media: Our product PDFreactor, a HTML-to-PDF converter, has been commercially available since 2006 and has supported JavaScript since 2012. Other commercial paged media user agents include Prince, supporting JavaScript since 2011, and Antenna House Formatter. The introduction of the '`page-size`' property and the new behavior of '`size`' would be an API change for the CSSOM and derived data structures. For functionalities that have been in production use for years, we'd appreciate if significant changes could be avoided. We'd like to suggest having another look at the approach where '`size`' is a shorthand everywhere and the `width` and `height` properties apply to pages, thus eliminating the need for the '`page-size`' property. We realize that `width` and `height` would be applied to the margin box for pages. However, we don't think that this would create significant confusion. Most importantly, this approach would not cause any breaking changes for authors at all. Please note that we even encountered customers that found it counter-intuitive that width and height cannot be set on pages. -- GitHub Notification of comment by bernhardf-ro Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/820#issuecomment-544582026 using your GitHub account
Received on Monday, 21 October 2019 15:58:21 UTC