Re: [csswg-drafts] [css-align] "Baseline Content-Alignment" spec text seems to incorrectly assume that align-content axis is always block axis

Let me compare two examples to make my thoughts a bit clearer.

SCENARIO 1:
````
  <flexcontainer id="a">
    <flexcontainer id="b" style="align-content: baseline">
````

Here, `#a` will think that its flex item `#b` should participate in baseline content alignment within its flex line, because the flex item (`#b`) has `align-content: baseline` and its inline axis is parallel to the flex container `#a`'s main axis.  So when `#a` is positioning/sizing items in its flex line, it may effectively give `#b` a bit of extra "virtual padding-top", so that it's aligned as part of that flex line's baseline group.

Thoughts: It makes some sense for `align-content` to have this kind of effect, because in this scenario, `align-content` is *supposed* to be doing some vertical alignment on the contents of `#b`. That's the axis that it operates in.

SCENARIO 2: consider an example like this, where I've simply added `flex-direction:column`:
````
  <flexcontainer id="a">
    <flexcontainer id="b" style="align-content: baseline; flex-direction: column">
````

Here, `#a` might still think it should apply some extra padding-top, because the same logic applies.  But in this case, it's kinda nonsensical because here, `#b`'s align-content axis is really the horizontal axis.

-- 
GitHub Notification of comment by dholbert
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3005#issuecomment-411928381 using your GitHub account

Received on Thursday, 9 August 2018 23:22:10 UTC