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

Re: [csswg-drafts] [css-flexbox][css-grid] Spec doesn't say whether "overflow: [non-visible]" on flex/grid container triggers a different baseline (as it does for inline-block)

From: Daniel Holbert via GitHub <sysbot+gh@w3.org>
Date: Wed, 25 Jul 2018 23:15:06 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-407925809-1532560505-sysbot+gh@w3.org>
> so the usual rules apply: last paragraph of https://drafts.csswg.org/css-align/#baseline-export

Thanks -- that chunk of spec text does seem like the most relevant text that describes what should happen here (for `inline-grid` and `inline-flex`).

Having said that -- it seems quite weird that `inline-block` gets this special case of degenerate behavior, since `inline-block` is the *easiest* container to find/visualize the baseline, as compared to `inline-grid`/`inline-flex`.  Is there a reason for this difference between the containers?  (Are we just in a case where we've decided CSS21 was silly/wrong to require this behavior, and we can't change it now, and we're trying to define newer containers to be smarter?)

-- 
GitHub Notification of comment by dholbert
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2902#issuecomment-407925809 using your GitHub account
Received on Wednesday, 25 July 2018 23:15:11 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 25 July 2018 23:15:12 UTC