As noted in bug 1455976 15, there's some special-case flexbox spec text for table wrapper boxes as flex items (pulling info from their child table boxes): # like width and height, the flex longhands # apply to the table box as follows: the flex item’s # final size is calculated by performing layout as if # the distance between the table wrapper box’s edges # and the table box’s content edges were all part of # the table box’s border+padding area, and the # table box were the flex item. https://drafts.csswg.org/css-flexbox/#flex-items This will end up making us *behave* as if a display:table flex child were a growable/shrinkable flex item like any other (but possibly with some extra space reserved for the wrapper box, e.g. if there's a caption that requires more space in the main axis than we'd otherwise allocate for our flex base size). I think this will require a bit of special-case code during the "resolve the flexible lengths" chunk of flex layout, as well as everywhere that we deal with a flex item's hypothetical size (e.g. when figuring out how many flex items fit on a multiline flex container's flex line).
Bug 1456224 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
As noted in bug 1455976 comment 15, there's some special-case flexbox spec text for table wrapper boxes as flex items (pulling info from their child table boxes): # like width and height, the flex longhands # apply to the table box as follows: the flex item’s # final size is calculated by performing layout as if # the distance between the table wrapper box’s edges # and the table box’s content edges were all part of # the table box’s border+padding area, and the # table box were the flex item. https://drafts.csswg.org/css-flexbox/#flex-items This will end up making us *behave* as if a display:table flex child were a growable/shrinkable flex item like any other (but possibly with some extra space reserved for the wrapper box, e.g. if there's a caption that requires more space in the main axis than we'd otherwise allocate for our flex base size). I think this will require a bit of special-case code during the "resolve the flexible lengths" chunk of flex layout, as well as everywhere that we deal with a flex item's hypothetical size (e.g. when figuring out how many flex items fit on a multiline flex container's flex line).