- From: Sergio via GitHub <sysbot+gh@w3.org>
- Date: Fri, 18 Aug 2017 14:29:18 +0000
- To: public-css-archive@w3.org
> I'm leaning towards yes, since having fit-content() behave exactly like auto aside from clamping at its argument seems like a useful and friendly behavior, but other thoughts welcome~ That's was my first thought when @mrego told me about the issue. Whoever (now with my implementor hat on) there are edge cases. For example, what about a fit-content(100px) track hosting a 200px item? It'll be sized to 200px, so we have already surpased the limit, would it make sense not to stretch it? I don't know :smile: I guess we need the opinion of the authors here to know what do they expect. >From the implementation POV I think either solution would be fine anyway. -- GitHub Notification of comment by svillar Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1732#issuecomment-323369046 using your GitHub account
Received on Friday, 18 August 2017 14:29:22 UTC