Re: [csswg-drafts] [css-flexbox] Investigate applying align-content to single-line flex containers

The CSS Working Group just discussed `flexbox`.

<details><summary>The full IRC log of that discussion</summary>
&lt;eae> Topic: flexbox<br>
&lt;astearns> github: https://github.com/w3c/csswg-drafts/issues/3052<br>
&lt;eae> TabAtkins: Align content for a flexbox, you can do align content on a muiltline flexbox but a single line flexbox does not respond to align content<br>
&lt;eae> ...this is beacuse we have a behavior where we stretch the line. Not super happy that we made that choice.<br>
&lt;eae> ...the problem is there are cases where there are cases where we'd like to align for single line. specifically for things like baseline alignment.<br>
&lt;eae> TabAtkins: By the current definition we can't do anything about it, it is always stretching. We can't add in the fake margin to cause it to align<br>
&lt;eae> fantasai:  the lines are stretched but the individual items arent, if you want ot baseline align you can't do that.<br>
&lt;eae> TabAtkins: only moves the line, not the items.<br>
&lt;eae> fantasai: The proposal is to take apply to single line flex containers, would allow more alignment options for flexboxes. Not a good reason it isn't allowed alreayd. Main concern is whether it is web compatible.<br>
&lt;eae> TabAtkins: use cases, baseline alignment, no reason why a single line shouldn't be allowed to align but a multi-line does.<br>
&lt;eae> florian: A similar use case is when making lines, requires wrapping for alignment to work. Declaring it to wrap has caused it tow rok, I don<br>
&lt;eae> 't need wrapping but it isn't causing any problems. What's the problem with having to declare wrap.<br>
&lt;eae> TabAtkins: Not consistent with not wanting wrapping.<br>
&lt;Chris_Lilley> zakim, remind us in 4 hours to go home<br>
&lt;Zakim> ok, Chris_Lilley<br>
&lt;eae> cbiesinger: Makes sense but please explain baseline items vs lines<br>
&lt;eae> s/baseline/align/<br>
&lt;eae> ??: the idea that long term that people have to know that wrpa is needed isn't ideal./ Better to have something that works for single line.<br>
&lt;astearns> s/??/jensimmons<br>
&lt;eae> TabAtkins: compat risk is in two cases, single line row of flex containers and non-auto cross size. Shrinking to the sdize of the elements anyway.<br>
&lt;cbiesinger> s/baseline items/baseline align items/<br>
&lt;eae> fantasai: If you did self alignment which pushes everyhting to the top and everything is shrink wrapped and the flex container is taller, you then have extra space.<br>
&lt;eae> TabAtkins: Auto-height won't have the problem.<br>
&lt;fantasai> TabAtkins: Fixed height will<br>
&lt;eae> TabAtkins: A column flexbox whos columns are all fixed with would have changed behavior with this proposal<br>
&lt;eae> TabAtkins: Those are likely to be rare cases.<br>
&lt;eae> fantasai: We probably want to run a use counter on this before committing to it.<br>
&lt;eae> florian: Either that or chrome tires it and reports back.<br>
&lt;eae> astearns: Preferences?<br>
&lt;eae> cbiesinger: I'd rather do a use counter<br>
&lt;eae> TabAtkins: I'll open a crbug.<br>
&lt;eae> astearns: Collect data and report back?<br>
&lt;eae> TabAtkins: Yes<br>
&lt;eae> astearns: objections?<br>
&lt;eae> astearns: We'll wait on data.<br>
&lt;eae> dbaron: Are we going to revisit once we have data?<br>
&lt;eae> astearns: yes<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3052#issuecomment-431808129 using your GitHub account

Received on Monday, 22 October 2018 18:27:53 UTC