- From: CSS Meeting Bot via GitHub <noreply@w3.org>
- Date: Thu, 21 Aug 2025 14:27:51 +0000
- To: public-css-archive@w3.org
The Houdini Task Force just discussed `[css-sizing] How to handle min-content being bigger than max-content?`, and agreed to the following: * `RESOLVED: if min-content is > max-content, floor max-content to match` <details><summary>The full IRC log of that discussion</summary> <alisonmaher> oriol: if you have elements w/ neg margin and place all on same line, you can get smaller size than if you break after each<br> <alisonmaher> ...algo for min/max content relies on the oposite. You can get max size smaller than min<br> <alisonmaher> ...this was breaking asserts<br> <alisonmaher> ...firefox accepts this as fine<br> <alisonmaher> ...blink in the inline block case used smaller, in flex it is the bigger one<br> <alisonmaher> ...webkit floored to zero for items, but sometimes get extra space<br> <alisonmaher> ...in servo I took max of max/min content for the max-content<br> <alisonmaher> ... should be more inteligent rather than breaking everywhere<br> <alisonmaher> ...?? that seems hard to do<br> <alisonmaher> ... dbaron proposed this. Would be good to get his thoughts<br> <alisonmaher> TabAtkins: the other part of his comment is that max content calc is prob correct, and shouldnt' have min content less than max if we can avoid<br> <alisonmaher> ...I think we can resolve min content should be <= max content<br> <alisonmaher> ...talk to dbaron about if clamp or more smart heuristic<br> <alisonmaher> florian: even if wrapping makes you larger, and infinite space, you won't wrap<br> <alisonmaher> TabAtkins: if you have small space could do something smarter<br> <alisonmaher> dbaron: I don't have a strong opinion<br> <alisonmaher> ...want to have min and max be coherent and wanting to get right result push in opposite directions<br> <alisonmaher> TabAtkins: min work is to clamp min by max content size<br> <alisonmaher> emilio: that isn't a lot of work<br> <alisonmaher> florian: if you do this and layout at min content, you will overflow<br> <alisonmaher> ...that isn't gret<br> <alisonmaher> iank_: pref oriol's proposal. We clamp in other cases for blink<br> <alisonmaher> ...surprised by line layout, need to investigate<br> <alisonmaher> fantasai: can see doing something different for text<br> <alisonmaher> ...for inline layout a good way to do it to layout on one line and then pull chunks off of it<br> <alisonmaher> ...you don't want to do it piece by piece. It makes sense to start with one line and then go from there to decide breaks<br> <alisonmaher> iank_: we do max content that way. For min content we just use max content result<br> <alisonmaher> ...have fast path and slow path. Think that is what is going on<br> <alisonmaher> ...we do max content as you describe though<br> <alisonmaher> oriol: clamping min content - what's weird is that you start adding 1px wide items at end, eventually increases max content, and then no longer need to clamp<br> <alisonmaher> fantasai: the problem of clamping is that if you have a box to layout into, lay it out at max content, put wrappable content in it. Suppsed to hit, but hit edge before you put everything in, then you wrap<br> <alisonmaher> ...then aren't operating at max content anymore and can overflow<br> <alisonmaher> ...that doesn't work because we don't layout at once<br> <alisonmaher> ...need to floor max by min content<br> <alisonmaher> oriol: that is what servo does<br> <alisonmaher> TabAtkins: min wins<br> <alisonmaher> iank_: good with that<br> <alisonmaher> oriol: there is a test for flex that follows this<br> <alisonmaher> ...blink was inconsistent in inline case<br> <alisonmaher> florian: maybe browser can come up with a different intelligent behvior<br> <alisonmaher> TabAtkins: that's possible<br> <alisonmaher> PROPOSED: if min-content is > max-content, floor max-content to match<br> <alisonmaher> RESOLVED: if min-content is > max-content, floor max-content to match<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12076#issuecomment-3210845970 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 21 August 2025 14:27:52 UTC