W3C home > Mailing lists > Public > public-css-archive@w3.org > May 2017

Re: [csswg-drafts] [css-values] clarify that most (all?) high-dpi devices anchor on pixel, rather than physical, unit

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Wed, 24 May 2017 16:34:15 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-303779713-1495643654-sysbot+gh@w3.org>
The CSS Working Group just discussed `[css-values] clarify that most (all?) high-dpi devices anchor on pixel, rather than physical, unit`, and agreed to the following resolutions:

* `RESOLVED: Move the close parens afte r"including high-resolution devices"`

<details><summary>The full IRC log of that discussion</summary>
&lt;zcorpan> Topic: [css-values] clarify that most (all?) high-dpi devices anchor on pixel, rather than physical, unit<br>
&lt;dbaron> that went to the wrong github issue<br>
&lt;zcorpan> Github topic: https://github.com/w3c/csswg-drafts/issues/708<br>
&lt;zcorpan> fantasai: PR for ???<br>
&lt;zcorpan> fantasai: reviewing the changes to update V&amp;U spec<br>
&lt;zcorpan> fantasai: one implemented the resolution here<br>
&lt;zcorpan> fantasai: also switch the ... anchor category<br>
&lt;zcorpan> fantasai: 2 categories for anchor units<br>
&lt;zcorpan> fantasai: pixel viewing angle unit<br>
&lt;zcorpan> fantasai: other is physical unit<br>
&lt;zcorpan> fantasai: css is based on 96 DPI and px is viewing angle<br>
&lt;zcorpan> fantasai: used to be independent but changed due to web compat<br>
&lt;zcorpan> fantasai: when you print, 12pt is actually 12pt<br>
&lt;zcorpan> fantasai: on screen we do the 96DPI thing and round to actual pixels to make it look nice on the screen<br>
&lt;zcorpan> fantasai: print and high-dpi together...<br>
&lt;zcorpan> fantasai: the change also moved devices with unusual viewing distances<br>
&lt;zcorpan> fantasai: so for print with unusual viewing distance, which category?<br>
&lt;zcorpan> fantasai: now it's in the physical category<br>
&lt;zcorpan> fantasai: do we want to revert the change?<br>
&lt;zcorpan> Rossen_: So, going to echo florian's point...<br>
&lt;zcorpan> Rossen_: since this is a SHOULD, do we need to change?<br>
&lt;dbaron> seems like if you're taking content written for another device and print it on a billboard, you want your "12pt" font to be bigger than 12pt<br>
&lt;zcorpan> fantasai: if we don't have anything we want to change we shouldn't change from the previous PR<br>
&lt;zcorpan> dbaron: the change seems reasonable to me<br>
&lt;zcorpan> dbaron: if you take content designed from a different device and print to a billboard you may want the viewing distance thing<br>
&lt;zcorpan> dbaron: OTOH if you design for the billboard you may want physical units<br>
&lt;dbaron> plinss: seems like this should be a choice when you're printing<br>
&lt;zcorpan> plinss: not happy with either change<br>
&lt;tantek> where is the change?<br>
&lt;zcorpan> plinss: it's a print-time choice based on the content, device, etc<br>
&lt;zcorpan> plinss: shouldn't mandate from the spec<br>
&lt;zcorpan> Rossen_: right, that's why it's a should<br>
&lt;astearns> tantek: https://github.com/w3c/csswg-drafts/pull/713/files<br>
&lt;zcorpan> Rossen_: might be enough<br>
&lt;fantasai> tantek, https://github.com/w3c/csswg-drafts/pull/713/files<br>
&lt;zcorpan> plinss: I think that's not what should means<br>
&lt;zcorpan> bradk: seems like a viewing angle situation<br>
&lt;zcorpan> bradk: language an opt-in, in ebook(?) you can go either way<br>
&lt;zcorpan> fremy: can't you leave it as choice per device?<br>
&lt;zcorpan> plinss: need all devices to be consistent<br>
&lt;bradk> s/ebook/e-paper<br>
&lt;zcorpan> tantek: i'm confused by the example of billboard vs print<br>
&lt;zcorpan> fantasai: it's an example of a device with an unusual viewing distance<br>
&lt;zcorpan> tantek: looking at the diff in github... billboard can be print or screen<br>
&lt;zcorpan> dbaron: the PR changed printed billboard because of the way it worded it<br>
&lt;zcorpan> fantasai: [citing spec?]<br>
&lt;zcorpan> fantasai: not a subset of screen media<br>
&lt;zcorpan> fantasai: 1 category is high-res, second is low-res and unusual viewing distance<br>
&lt;zcorpan> fantasai: before you could interpret print with unusual viewing distance as either<br>
&lt;zcorpan> fantasai: now it can only be that for screen media<br>
&lt;zcorpan> fantasai: becomes ???<br>
&lt;zcorpan> someone: sounds sensible<br>
&lt;fantasai> Proposal is to move the lcose parentheses after "including high-resolution devices"<br>
&lt;fantasai> s/someone/tantek/<br>
&lt;Rossen_> For screen media (including high-resolution devices), lower-resolution devices,   and devices with unusual viewing distances,<br>
&lt;zcorpan> Rossen_: sounds pretty good<br>
&lt;astearns> s/,   /, /<br>
&lt;bradk> I agree<br>
&lt;zcorpan> fantasai: ok, i will make the change<br>
&lt;zcorpan> plinss: happy with the change<br>
&lt;zcorpan> plinss: maybe provide an opt-in later<br>
&lt;fantasai> ScribeNick: fantasai<br>
&lt;zcorpan> Proposed resolution:  move the lcose parentheses after "including high-resolution devices"<br>
&lt;tantek> +1 to proposal<br>
&lt;fantasai> RESOLVED: Move the close parens afte r"including high-resolution devices"<br>
&lt;myles> scribenick: myles<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/708#issuecomment-303779713 using your GitHub account
Received on Wednesday, 24 May 2017 16:34:22 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:13 UTC