- From: Nick Sherman via GitHub <sysbot+gh@w3.org>
- Date: Tue, 15 Nov 2016 12:11:31 +0000
- To: public-css-archive@w3.org
@patrickhlauke Yes there are several interesting questions related to this. Some of them are more complex than others, and while I personally have opinions in many cases (perhaps better elaborated elsewhere if we want to keep this thread on topic), I can’t claim to be an authority on all of them. Nevertheless, I don’t think questions like these should be the reason that physical units are entirely ignored. I’ve done a few rounds of tests using the existing “absolute” units with typical consumer-level software and hardware, and every time I’ve had inaccurate results like the ones you showed. What’s worse is that the results vary widely depending on factors that are very hard if not impossible to pin down with certainty. The sizing error you showed seems small at the target size of 1 inch, but that’s already enough to be unusable for many production purposes. And if you multiply that scaling error up to a target size of 10+ inches, it literally becomes a big problem. Most of this conversation has been focused around the idea of _sizing elements_ with physical units, which is great, but I feel inclined to also point out the less-obvious benefit of being able to query again physical sizes. For example, I'd love to be able to specify separate layouts for 8.5×11″ and 11×17″ paper formats, etc. -- GitHub Notification of comment by nicksherman Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/614#issuecomment-260625318 using your GitHub account
Received on Tuesday, 15 November 2016 12:11:37 UTC