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

The CSS Working Group just discussed `[css-writing-modes] Orthogonal Flow Constraint: viewport vs scroller`, and agreed to the following resolutions:

* `RESOLVED: shrink-to-fit formula for auto-sized orthogonal flows uses nearest scrollable ancestor, not necessarily viewport`

<details><summary>The full IRC log of that discussion</summary>
&lt;zcorpan> Topic: [css-writing-modes] Orthogonal Flow Constraint: viewport vs scroller<br>
&lt;Rossen_> https://github.com/w3c/csswg-drafts/issues/1391<br>
&lt;zcorpan> fantasai: Realized that I hadn't done ???<br>
&lt;Rossen_> Github issue: https://github.com/w3c/csswg-drafts/issues/1391<br>
&lt;zcorpan> fantasai: we have 2 impl and a test that i need to check in<br>
&lt;zcorpan> fantasai: the issue is about when you have orthogonal flows and a scroller<br>
&lt;zcorpan> fantasai: normally when htere's no constraint of the child... the height is determined by a shink-to-fit formula<br>
&lt;zcorpan> fantasai: better to use the hight of the nearest ancestor<br>
&lt;zcorpan> Rossen_: I recall discussing this<br>
&lt;fantasai> s/nearest ancestor/nearest scrollable ancestor/<br>
&lt;zcorpan> Rossen_: we already agreed to do this for the reasons you outline<br>
&lt;zcorpan> Rossen_: are there any other opinions or alternative proposals?<br>
&lt;zcorpan> Rossen_: if not we can just resolve<br>
&lt;zcorpan> Rossen_: I will take that as a no<br>
&lt;fantasai> RESOLVED: shrink-to-fit formula for auto-sized orthogonal flows uses nearest scrollable ancestor, not necessarily viewport<br>
&lt;zcorpan> Rossen_: Does that change go to Level 1?<br>
&lt;fantasai> s/1/3/<br>
&lt;zcorpan> Rossen_: any other knobs or switches ?<br>
&lt;zcorpan> fantasai: we have the change, the WG resolution, test case and implementations<br>
&lt;zcorpan> Rossen_: ok great<br>
&lt;Rossen_> Github topic: https://github.com/w3c/csswg-drafts/issues/708<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-303775339 using your GitHub account

Received on Wednesday, 24 May 2017 16:19:17 UTC