Re: [csswg-drafts] [css-writing-modes] Orthogonal Flow Constraint: viewport vs scroller

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

-- 
GitHub Notification of comment by atanassov
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1391#issuecomment-303775738 using your GitHub account

Received on Wednesday, 24 May 2017 16:20:54 UTC