Re: [csswg-drafts] [css-grid] Resolution of percentage row tracks and gutters with indefinite height (#5566)

The CSS Working Group just discussed `Resolution of percentage row tracks and gutters with indefinite height`.

<details><summary>The full IRC log of that discussion</summary>
&lt;heycam> Topic: Resolution of percentage row tracks and gutters with indefinite height<br>
&lt;heycam> github: https://github.com/w3c/csswg-drafts/issues/5566<br>
&lt;heycam> rego: this is an old discussion<br>
&lt;heycam> ... this is about how we resolve percetange row tracks/gutters<br>
&lt;heycam> ... with a minimum height<br>
&lt;heycam> ... we resolve to intrinsic height that we compute<br>
&lt;heycam> ... that causes overflow in many cases<br>
&lt;heycam> ... and makes it more complicated, and no interop<br>
&lt;heycam> ... in Firefox it is doing the old behavior.  %age tracks resolve to auto<br>
&lt;heycam> ... I was proposing here to change again, and get interop in this case<br>
&lt;heycam> ... and then also change how gutters work, which Firefox does do<br>
&lt;heycam> ... we have been discussing for a long time, checking compat issues, we already had a use counter for %age tracks, also for gutters<br>
&lt;Rossen_> q?<br>
&lt;heycam> ... checking the results, grid tracks where 0.03% of page views<br>
&lt;heycam> ... that's going down, to not count 1 row with 100%<br>
&lt;heycam> ... we analyzed the pages from that, only 1 broke<br>
&lt;heycam> ... with gutters, the usage is very low. 0.003% of page views<br>
&lt;heycam> ... 40 pages, only 1 broke<br>
&lt;heycam> ... so this change will align us with flexbox, and get interop in the tracks part that we don't have right now<br>
&lt;heycam> Rossen_: we did discuss this in the past, in the context of flexbox, grid and gutters.  every time the discussion goes around and comes back to one of the main points/principles for grid<br>
&lt;heycam> ... which is to hold the behavior of rows and columns, and row gutters / col gutters, to be symmetric<br>
&lt;heycam> ... strong desire for this<br>
&lt;heycam> ... strong pushback against things going against this principle<br>
&lt;heycam> ... don't want to relitigate that<br>
&lt;heycam> ... so why should we change it for this one?<br>
&lt;heycam> rego: it will break that principle.  the reasons we should change are in the top of the issue<br>
&lt;heycam> ... it usually causes overflow when people use it<br>
&lt;heycam> ... it requires worse perf in track sizing<br>
&lt;heycam> ... and we don't have interop<br>
&lt;heycam> ... but I agree it will break that principle<br>
&lt;Rossen_> q?<br>
&lt;heycam> Rossen_: would like to hear from more people.  personal preference to hold on to that principle<br>
&lt;heycam> ... it's an easy slippery slope to get on<br>
&lt;heycam> ... yes there are expectations when they compare other 1D layout systems like block and flexbox.<br>
&lt;heycam> ... with this particular one, I think we should hold a high bar in keeping that principle going forward<br>
&lt;heycam> jensimmons: I haven't heard much about this kind of stuff at all<br>
&lt;heycam> ... feel like authors haven't quite grasped grid fully yet<br>
&lt;heycam> ... lack of compat is a problem, would like interop asap, even if the behaviour feels a bit buggy<br>
&lt;heycam> ... and stop using percents for gutters anyway<br>
&lt;heycam> ... so in some ways I don't really care about this, since they shouldn't be using percentages<br>
&lt;heycam> Rossen_: I think the data agrees with your observations, few cases in the wild<br>
&lt;heycam> ... doesn't feel like it's strongly motivated<br>
&lt;heycam> miriam: that's my experience as well<br>
&lt;heycam> fantasai: I think it'd be good to hear from mats and rachel<br>
&lt;heycam> ... if nobody else had anything else to add, could defer to hear from them<br>
&lt;heycam> Rossen_: in the meantime we can publish grid-1 and grid-2 as CRDs<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5566#issuecomment-712430984 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Monday, 19 October 2020 20:43:39 UTC