- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 13 Feb 2019 18:00:48 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `Empty grid tracks should contribute to scrollable overflow`. <details><summary>The full IRC log of that discussion</summary> <dael> Topic: Empty grid tracks should contribute to scrollable overflow<br> <dael> github: https://github.com/w3c/csswg-drafts/issues/3638<br> <dael> astearns: Short intro to this topic<br> <dael> fantasai: Filed by someone using empty grid tracks. It was showing...it's in a scrollable grid container and spacing left by empty ttracks not showing in FF b/c different interpretations. Should scrollable overflow area of grid container be only big enought ot cotnaint elements or big enough for entire explicit grid. It's an abstraction that's not a box<br> <dael> TabAtkins: Grid exists like flex lines. It's not a thing in thebox tree<br> <dael> fantasai: Argument against is impl that's the only thing that's real. Authors expect inluding all grid tracks<br> <dael> Rossen: A grid element that itself is overflow scroll?<br> <dael> fantasai: A grid container that's overflow:scroll with a bunch of tracks and some items in it.<br> <dael> TabAtkins: Items in the grid fit within the visible area, but tracks don't. Scrollbar or no?<br> <dael> jensimmons: Super itneresting. If authors have extra tracks I think they would expect to scroll<br> <dael> rachelandrew: Authors would expect a scrollbar. They expect the grid to be real<br> <dael> plinss[m]: Would you expect it to size to explicit grid lines if it's not overflow:scroll?<br> <dael> fantasai: It does<br> <dael> plinss[m]: Bheavior should be consistent<br> <dael> Rossen: Are you saying the intrinsic size of the grid is the extent for scrolling?<br> <dael> plinss[m]: Yes<br> <dael> astearns: We're at time. That's an intro for this issue. It's an interesting one and we should discuss in the future.<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3638#issuecomment-463302175 using your GitHub account
Received on Wednesday, 13 February 2019 18:00:50 UTC