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

Re: [csswg-drafts] [css-sizing] Restrict 'stretch' and 'fit-content' to width/height and max-*

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Wed, 01 Nov 2017 23:33:59 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-341274397-1509579238-sysbot+gh@w3.org>
The Working Group just discussed `Restrict 'stretch' and 'fit-content' to width/height and max-*`.

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: Restrict 'stretch' and 'fit-content' to width/height and max-*<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/1913<br>
&lt;dael> fantasai: TabAtkins and I couldn't figure out a good use case for using them as a min width or height. We were suggesting to drop from min.<br>
&lt;dael> fantasai: I can't think of a single reason you want to do it so it's not worth effort on testing and impl.<br>
&lt;dael> astearns: This is L3 and L4 because you want to restrict fit-content function?<br>
&lt;dael> fantasai: Yes, I think so.<br>
&lt;dael> dbaron: I find it weird because it's about exposing low level concepts. Even if I can't come up with a use case it doesn't seem implausible. It's useful to have primitive concepts exposed when those concepts exist.<br>
&lt;dael> fantasai: Fair.<br>
&lt;dael> fantasai: I don't have a strong optinion.<br>
&lt;dbaron> s/use case/use case off the top of my head/<br>
&lt;dael> astearns: I'm wonndering if there is a case where you're using custom properties that are set to one of these things and it would make sense to use that custom prop value for a set of regular min and max prop. I'm not coming up with an actual case though.<br>
&lt;dael> astearns: dbaron would you rather have them put back in? Or are you okay with then off for now until someone comes up with a reason.<br>
&lt;dael> dbaron: I'd rather put back in, but I don't feel that strongly.<br>
&lt;dael> fantasai: Anyone else have an opinion?<br>
&lt;dael> fremy: I can't find a use case either, but I don't have a strong opinion. I wouldn't want either remove or added. Either is fine. I can understand both points.<br>
&lt;dael> astearns: What about if we leave this for a week and bring it up at TPAC with more people and more thought for possible use cases? Or just some stronger arguments for consistancy.<br>
&lt;dael> astearns: All I'm hearing is a lot of I'm not feeling strongly about this.<br>
&lt;dael> astearns: Is this okay to leave for now fantasai?<br>
&lt;dael> fantasai: No problem.<br>

GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1913#issuecomment-341274397 using your GitHub account
Received on Wednesday, 1 November 2017 23:34:05 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 1 November 2017 23:34:06 UTC