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

Re: [csswg-drafts] [css-flexbox] Non-interop with shrinking images

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Mon, 06 Nov 2017 22:02:32 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-342302648-1510005751-sysbot+gh@w3.org>
The Working Group just discussed `Non-interop of sizing images in flexbox`.

<details><summary>The full IRC log of that discussion</summary>
&lt;iank_> Topic: Non-interop of sizing images in flexbox<br>
&lt;astearns> github: https://github.com/w3c/csswg-drafts/issues/1322<br>
&lt;iank_> fantasai: &lt;goes to project><br>
&lt;iank_> fantasai: Testcase in last comment<br>
&lt;iank_> fantasai: Flex container, and has some content that shrink down to their min-content size, if you have too many items they'll start to overflow.<br>
&lt;iank_> fantasai: Excess space starts to take up, the text starts to break, &lt;explains the testcase><br>
&lt;iank_> fantasai: The item with the image starts shrinking.<br>
&lt;iank_> fantasai: This FF behaviour is kinda nice.<br>
&lt;iank_> fantasai: So we want to make FF follow the spec? Or make other vendors follow FF implmentation><br>
&lt;iank_> ?<br>
&lt;iank_> dholbert: I wrote most of the flex code in FF, and don't know whats going on here.<br>
&lt;iank_> gregwhitworth: What is the usecase where folks would want this behaviour?<br>
&lt;iank_> fantasai: This means that it won't overflow, where other implmentations would.<br>
&lt;iank_> dholbert: &lt;explains image gallery usecase> being able to shrink them is kinda nice.<br>
&lt;jensimmons> I just dropped this example in this codepen: https://codepen.io/jensimmons/pen/aVmogq<br>
&lt;iank_> fantasai: The image doesn't shrink until everything else has wrapped.<br>
&lt;iank_> cbiesinger: If you give the image a flex-basis: auto , and others a flex-basis of 0, don't you get that behaviour?<br>
&lt;iank_> fantasai: You wouldn't be able to get them to start out at their content sizes?<br>
&lt;iank_> fantasai: I don't think we need to resolve now, but interesting to think about.<br>
&lt;iank_> dholbert: I'll try and figure out whats happening in our impl, and report back on the github issue.<br>
&lt;iank_> jensimmons: I had a few questions about flexbox, lets of interop issues around squishing images, and because of those issues, they are really hard for authors to think about.<br>
&lt;iank_> astearns: Def. want interop here, just need to agree what that behaviour is.<br>
&lt;iank_> Rossen: It looks like we have all the impls apart from FF, having interop.<br>
&lt;iank_> Rossen: Switching to FF, means that we might run into compat.<br>
&lt;iank_> fantasai: We were going through interop cases, and most of them were obv., but this one seemed interesting.<br>
&lt;iank_> jensimmons: It also seems like we could do what we want, as there seems to be such lack of interop around images.<br>
&lt;iank_> gregwhitworth: Only about this issue?<br>
&lt;iank_> jensimmons: No, more broadly about images as flex items.<br>
&lt;iank_> gregwhitworth: Where are the bugs?<br>
&lt;iank_> fantasai: Don't have them here. But this one just seemed interesting.<br>

GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1322#issuecomment-342302648 using your GitHub account
Received on Monday, 6 November 2017 22:02:36 UTC

This archive was generated by hypermail 2.3.1 : Monday, 6 November 2017 22:02:38 UTC