W3C home > Mailing lists > Public > public-css-archive@w3.org > June 2018

Re: [csswg-drafts] [css-flexbox] flexbox spec isn't interoperable w/ existing implementations, RE `flex-basis` resolution for table wrapper box flex-items

From: Daniel Holbert via GitHub <sysbot+gh@w3.org>
Date: Wed, 20 Jun 2018 21:03:49 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-398896174-1529528628-sysbot+gh@w3.org>
Thanks for the response (and sorry for the long response time on my part).

I think you're right that the spec basically covers this; I was perhaps reading too much into the first sentence of the paragraph you quoted (*"the table wrapper box becomes the flex item"*), and not reading enough into the last sentence (*"perform layout as if...the table box were the flex item"*).  That last sentence is a bit hand-wavy, but in retrospect I guess it's a pretty strong requirement (and is not what Firefox/Edge seem to do now, FWIW, but seems like a reasonable thing to do).

So, bottom line, I think the direct answer to my original concern here is:
 - Yes, the used flex-basis on the table-wrapper box is indeed always "content"...
 - ...BUT that doesn't matter, because the above-quoted spec paragraph's last sentence says to perform layout as if the *table box* were the flex item (even though it's technically not).
 - So: in that spirit, we should be looking at the used flex-basis on the *table box* (which is *not* `content` in my example) and using that to determine the flex base size, resolve flexible lengths, etc.

So I think we're OK here.  Incidentally, https://bugzilla.mozilla.org/show_bug.cgi?id=1456224 is filed on bringing Firefox closer to what the spec requires on this point.

GitHub Notification of comment by dholbert
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2604#issuecomment-398896174 using your GitHub account
Received on Wednesday, 20 June 2018 21:03:55 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 19 September 2019 01:18:58 UTC