- From: Dave Crossland via GitHub <sysbot+gh@w3.org>
- Date: Sat, 23 May 2020 22:32:37 +0000
- To: public-css-archive@w3.org
> > I think that's the opposing position to the one @Lorp staked out today, which boils down to that the "actual" size ship sailed a long time ago, and attempting to fix that is way out of reach for us bunch of nerds > > I don't think it's an opposing position. I agree with Laurence that the relationship between physical size, nominal size, and applied size in our digital environments is basically uncertain. Okay good :) > I'm saying that type design can't address uncertainty, so if you want optically tuned design for different sizes of type, you need to _start_ from an absolute physical unit, even if where you go from there in implementation of type sizing is relative and flexible. What's wrong with using CSS (aka Device Independent) px as that unit? 1 CSS px = 1/96th of 1in 1 CSS pt = 1/72 of 1in Browsers are entrenched with mapping opsz values to the former. That's the fact. The ot spec needs to be updated to match this reality. Non px systems need to convert opsz values to pt; they don't exist yet and aren't entrenched. -- GitHub Notification of comment by davelab6 Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4430#issuecomment-633149040 using your GitHub account
Received on Saturday, 23 May 2020 22:32:38 UTC