- From: L. David Baron via GitHub <sysbot+gh@w3.org>
- Date: Wed, 24 May 2017 16:20:58 +0000
- To: public-css-archive@w3.org
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> <zcorpan> Topic: [css-writing-modes] Orthogonal Flow Constraint: viewport vs scroller<br> <Rossen_> https://github.com/w3c/csswg-drafts/issues/1391<br> <zcorpan> fantasai: Realized that I hadn't done ???<br> <Rossen_> Github issue: https://github.com/w3c/csswg-drafts/issues/1391<br> <zcorpan> fantasai: we have 2 impl and a test that i need to check in<br> <zcorpan> fantasai: the issue is about when you have orthogonal flows and a scroller<br> <zcorpan> fantasai: normally when htere's no constraint of the child... the height is determined by a shink-to-fit formula<br> <zcorpan> fantasai: better to use the hight of the nearest ancestor<br> <zcorpan> Rossen_: I recall discussing this<br> <fantasai> s/nearest ancestor/nearest scrollable ancestor/<br> <zcorpan> Rossen_: we already agreed to do this for the reasons you outline<br> <zcorpan> Rossen_: are there any other opinions or alternative proposals?<br> <zcorpan> Rossen_: if not we can just resolve<br> <zcorpan> Rossen_: I will take that as a no<br> <fantasai> RESOLVED: shrink-to-fit formula for auto-sized orthogonal flows uses nearest scrollable ancestor, not necessarily viewport<br> <zcorpan> Rossen_: Does that change go to Level 1?<br> <fantasai> s/1/3/<br> <zcorpan> Rossen_: any other knobs or switches ?<br> <zcorpan> fantasai: we have the change, the WG resolution, test case and implementations<br> <zcorpan> Rossen_: ok great<br> <Rossen_> Github topic: https://github.com/w3c/csswg-drafts/issues/708<br> </details> -- GitHub Notification of comment by dbaron Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1391#issuecomment-303775875 using your GitHub account
Received on Wednesday, 24 May 2017 16:21:04 UTC