This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
(see email thread) Currently, flexibility is always addition and subtraction, not multiplication or division. It makes sense when stretching - when items already have the space they wanted, they get equal share of additional space (given same flexibility). But when shrinking, subtraction isn't really a good way of fair distribution. It works OK with minor adjustments, but if space shortage is significant and some items are much bigger than others, small items quickly shrink to zero (or their min size), while big fat items may not even notice. The problem can be mitigated by giving bigger items bigger negative flex, but it is only possible if the author knows what will be bigger... Shrinking should be done by *dividing* the flexible lengths proportional to flexibility. Something like this: shrink-factor = sum(preferred-size / negative-flex) / available-space used-main-size = main-size / (shrink-factor * negative-flex) this way, when shrinking, flex items remain proportional to their preferred size.
correct formula for the desired result is this: space-shortage = sum(flex-basis) - available-space shrink-factor = space-shortage / sum(flex-basis * negative-flex)) main-size = flex-basis * (1 - shrink-factor * negative-flex)) (previous proposed formula immediately scales all items by their negative flex and gets divizion by zero when negative-flex is zero)
Done.