W3C home > Mailing lists > Public > public-css-archive@w3.org > November 2016

Re: [csswg-drafts] [css-grid] inconsistencies in the definition of grid container baselines

From: fantasai via GitHub <sysbot+gh@w3.org>
Date: Thu, 24 Nov 2016 09:54:38 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-262734994-1479981276-sysbot+gh@w3.org>
> What axis ? I think that text comes from the version which allowed 
block-axis baselines.


> The link 'alignment context' is broken.

Seems to be working for me.

> What does it means "synthesized according to the rules of its 
alignment context." ?

E.g. grids and flexboxes synthesize using the border edges of an item,
 whereas inline layout synthesizes using the margin edges of an inline
 box. We can't change the latter behavior due to compat. So we're 
restricted to inline-block need to use the margin edges. In that case,
 either all block containers use margin edges, or all inline-level 
boxes do, or everything does. Since treating empty block containers 
differently from empty grid or flex containers didn't seem reasonable,
 we narrowed down to either inline-level boxes use margins and 
flex/grid-level boxes use borders, or all boxes use margins. The 
discussion concluded on the former: 

> Why "if needed" ?

Sometimes you don't need to baseline-align the box. :)

There might also be an issue wrt propagation of baselines through 
ancestors here... meaning, we could say that synthesized baselines 
don't propagate to a parent the way natural ones do. I'm not recalling
 this line of reasoning very clearly atm, though.

GitHub Notification of comment by fantasai
Please view or discuss this issue at 
using your GitHub account
Received on Thursday, 24 November 2016 09:54:44 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:05 UTC