Re: [csswg-drafts] [css-grid-1][css-grid-2] Basic support for "equal gutter" with justify-content on grid items

The Working Group just discussed `[css-grid-1][css-grid-2] Basic support for "equal gutter" with justify-content on grid items`, and agreed to the following resolutions:

* `RESOLVED: Add the feature proposed in issue #1116 to Grid L2`
* `RESOLVED: Publish FPWD for Grid L2`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: [css-grid-1][css-grid-2] Basic support for "equal gutter" with justify-content on grid items<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/1116<br>
&lt;dael> Rossen_: This is, if I recall, the newly added functionality to Grid L2.<br>
&lt;dael> fantasai: There is a justify-content prop that takes values to be put inbetween. You can center tracks, space them to the left or right, kinda like flex items. When people have a grid they want to auto-distribute, but have equal spacing in both axes. Right now no way to get that.<br>
&lt;dael> fantasai: This proposal has a possible value where it means go look at the other direction and use it over here multiplied by a number.<br>
&lt;lajava> yes<br>
&lt;dael> Rossen_: Do we have lajava?<br>
&lt;dael> Rossen_: I see they've made comments on the issue.<br>
&lt;Rossen_> s/lajava/javifernandez/<br>
&lt;lajava> rego and me are attending from igalia<br>
&lt;dael> Rossen_: I read through them. Seems there could be ambig as to how this could be helpful.<br>
&lt;dael> fantasai: What proposal does is what was requested. I'm happy to entertain other syntatic options, but we should solve the problem. What happens in each case should be worked through. Stretch shouldn't be allowed in combo.<br>
&lt;dael> Rossen_: And from your proposed solutions you had 2 options. 1 to introduce a new syntax and the other was define what happens if axis is auto size and space is justified instead of copied. Which of the two proposals do you want to discuss?<br>
&lt;dael> fantasai: I'm happy to entertain either. I think the proposal without syntax don't allow different propostions and would also change existing behavior so probably not the way we can go as TabAtkins noted last March.<br>
&lt;dael> florian: The unitless number one seemed to make sense to me. I think TabAtkins has reservations about unitless numbers because they don't meshed will with typedOM.<br>
&lt;dael> fantasai: In this case it's a multiplier and I don't know what unit we'd want to introduce.<br>
&lt;dael> florian: It's a % of some kind that just doesn't say so.<br>
&lt;dael> fantasai: We could use % also.<br>
&lt;dael> florian: % Isn't used there?<br>
&lt;dael> fantasai: Just alignment keywords. We could add % to them in the future for the % of the amount from start to end. For that reason if we go in that direction it might be a good idea to not use %.<br>
&lt;dael> Rossen_: I would stay away from % as well.<br>
&lt;dael> fantasai: This effectively represents an aspect ratio of sorts.<br>
&lt;dael> florian: Fair enough.<br>
&lt;dael> florian: I don't mind. I just thought abfelt introducing unitless things makes other hthings worse.<br>
&lt;florian> s/abfelt/tab felt/<br>
&lt;dael> fantasai: If someone doesn't like this proposal and wants to work on an alternate that's fine, but I don't have another alternative.<br>
&lt;florian> it seems sensible to me.<br>
&lt;dael> Rossen_: I think this is a reasonable starting point. By the time we're done we might change, but as a starting point the proposed solution addresses this feature request.<br>
&lt;dael> Rossen_: I'd like to hear if there are other thoughts or proposals. If there are additional syntax issues we can deal separetely.<br>
&lt;dael> Rossen_: I'm not hearing pushback on the proposed way to solve and impl.<br>
&lt;dael> Rossen_: Are there any or any objections?<br>
&lt;rachelandrew> +1 to adding the feature<br>
&lt;dael> Rossen_: There's a fair interest in this feature. Others last week gave thumbs up. I think it's reasonable to accept as level 2.<br>
&lt;dael> Rossen_: Are there any objections or additional comments?<br>
&lt;dael> RESOLVED: Add the feature proposed in issue #1116 to Grid L2<br>
&lt;rego> lajava, is having problems with the mic<br>
&lt;dael> fantasai: Do we want to do FPWD?<br>
&lt;fantasai> rego, maybe type in comment into IRC and we'll relay?<br>
&lt;lajava> yes, sorry, nothing urgent that can't be dicussed offline<br>
&lt;dael> Rossen_: Exactly. We can proceed to now resolve on FPWD for grid. Which will be potentially all the L1 delta incl subgrid and this new grid gutter feature<br>
&lt;dael> Rossen_: I believe that's everything in L2, right?<br>
&lt;Chris_> so is the document ready to go for fpwd or does it need edits first?<br>
&lt;rego> we don't have a better proposal, but we've some doubts regarding how it'll work for grid containers with "height: auto", if after alignment it'll overflow or if it'll change the height of the container<br>
&lt;dael> fantasai: Yeah, this is all I intend for L2. We should focus on subgrid and this feature was straightfoward.<br>
&lt;rego> but as we don't have a better proposal, I believe current one is fine as strating point<br>
&lt;dael> Rossen_: Yeah. On our end we reviewed and we're fine with FPWD.<br>
&lt;Chris_> I prefer that we are ready to go before resolving to request the transition<br>
&lt;lajava> my concerns are specially related to the fact tha Content Distibution increase the size of the contauner, instead of using the available space (even causing overflow)<br>
&lt;tantek> ship it<br>
&lt;dael> Rossen_: If there are no obj we'll resolve.<br>
&lt;dael> Chris_: The doc is ready to go as is now? features we want are in?<br>
&lt;dael> fantasai: Yes, just need to be regenerated.<br>
&lt;dael> Rossen_: There's no features we don't want. I had reservations last week, but we reviewed and we're good.<br>
&lt;dael> Chris_: +1<br>
&lt;dael> RESOLVED: Publish FPWD for Grid L2<br>
&lt;fantasai> lajava, rego: These are good points, let's work through them in WD.<br>
&lt;dael> Rossen_: Congrats and thank you.<br>
</details>


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

Received on Wednesday, 31 January 2018 17:18:13 UTC