W3C home > Mailing lists > Public > public-css-archive@w3.org > September 2017

Re: [csswg-drafts] [css-grid] fit-content() vs 'stretch' alignment

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Wed, 20 Sep 2017 17:01:08 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-330915960-1505926856-sysbot+gh@w3.org>
The Working Group just discussed `fit-content() vs 'stretch' alignment`, and agreed to the following resolutions:

* `RESOLVED: fit-content does not grow past its arguement due to alignment stretch`
* `RESOLVED: keep fit-content behavior as-is, to not grow past max-content in presense of stretch`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: fit-content() vs 'stretch' alignment<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/1732<br>
&lt;dael> Rossen_: fantasai can you take this?<br>
&lt;dael> fantasai: I haven't looked lately. Looking now.<br>
&lt;dael> Rossen_: I think you brought this up 3 weeks ago.<br>
&lt;dael> fantasai: I think in order to make progress on writing modes we should do florian's extra.<br>
&lt;dael> Rossen_: Grid issue you want to discuss on GH?<br>
&lt;fantasai> https://github.com/w3c/csswg-drafts/issues/1732<br>
&lt;dael> fantasai: no...it's okay.<br>
&lt;dael> fantasai: Issue was we have a stretch value for alignt and justify content. These align and justify grid tracks from a high level. One of the options is strech, kinda like flex lines. If you choose stretch we do so by distributing space to auto-size columsn euqually.  No auto sized columns, nothing happens.<br>
&lt;dael> fantasai: Q is if it should apply to fit-content or not. Looks like rachelandrew asked a few authors and they expect it not to go past argumenet of fit content, but there was a question of should we apply the extra space at all.<br>
&lt;dael> fantasai: WE can say fit content doesn't go past its argumenet due to stretching.<br>
&lt;dael> Rossen_: I'm in favor as an impl.<br>
&lt;fantasai> s/WE/For sure I think we/<br>
&lt;dael> Rossen_: Obj to resolving that fit-content does not grow past its arguement due to alignment stretch.<br>
&lt;dael> RESOLVED: fit-content does not grow past its arguement due to alignment stretch<br>
&lt;rachelandrew> this was the issue as it came up https://github.com/rachelandrew/gridbugs/issues/9<br>
&lt;dael> fantasai: Second is should fit-content grow past it's max content...if we're below the argument, the clamping one, do we grow fit-content it the stretch is set.<br>
&lt;dael> fantasai: For that question, I don't know. We don't seem to have any feedback one way or another of what should happen there.<br>
&lt;dael> jensimmons: Alternately the content would not stretch?<br>
&lt;dael> fantasai: If there's auto tracks there, if not start.<br>
&lt;dael> jensimmons: And they could adjust by not using stretch?<br>
&lt;dael> fantasai: Yes, case where it would make a difference is if there's fit-content and an auto column. They have very similar behavior except fit-content has additional clamp.<br>
&lt;dael> Rossen_: This scenario was a canonical example we had originally when working on grid. The ability to have a menu system based on size of items inside and let the extra space go into the rest of the content area. Using fit-content with auto columns or fr columns was the way to achieve this.<br>
&lt;dael> Rossen_: If you take away the guar. of fit-content that's not just for grid and we start changing what fit-content means then this is a pretty, in my opinion, radiacal change.<br>
&lt;dael> Rossen_: I haven't seen any really strong cases to change that and I would prefer if we don't (as an impl)<br>
&lt;dael> jensimmons: You want to stretch beyond max-content?<br>
&lt;dael> Rossen_: I don't.<br>
&lt;dael> fantasai: Auto will go beyond max-content, but fit-content won't.<br>
&lt;dael> Rossen_: fit-content was designed to fit content<br>
&lt;dael> rachelandrew: I'd agree with Rossen_ I don't think people would expect it to stretch. I'd prefer fit-content stays the way it is.<br>
&lt;dael> Rossen_: We're at top of hour.<br>
&lt;dael> fantasai: We should go for resolving<br>
&lt;tantek> +1<br>
&lt;dael> Rossen_: Obj to keep fit-content behavior as-is, to not grow past max-content in presense of stretch<br>
&lt;dael> RESOLVED: keep fit-content behavior as-is, to not grow past max-content in presense of stretch<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1732#issuecomment-330915960 using your GitHub account
Received on Wednesday, 20 September 2017 17:01:00 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:18 UTC