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

The CSS Working Group just discussed `[css-flexbox] Investigate applying align-content to single-line flex containers  Proposed Resolution: close this as Rejected due to web compat`.

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: [css-flexbox] Investigate applying align-content to single-line flex containers  Proposed Resolution: close this as Rejected due to web compat<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/3052#issuecomment-1226112918<br>
&lt;dael> astearns: Proposed resoution is no<br>
&lt;dael> fantasai: When flex was released we defined align content only applies to multiline. Aligns the flex lines. COuld apply to single line in which case you could top align a bunch of flex items and then center align the line<br>
&lt;dael> fantasai: Seems there are enough web pages expecting it to not have an effect that we could not change based on chrome data. We think we can't fix this and should add to list of mistakes<br>
&lt;dael> iank_: I looked last week quickly at use counter. It will overcount potentially. But it's high enough that there are sites taht will rely on this so I'm fine. Could do a sample of sites but it's fine<br>
&lt;dael> astearns: If you're worried about overcounting by an oder of magnitude<br>
&lt;dael> iank_: Even if it is it's a large number of sites<br>
&lt;dael> fantasai: Yeah. I think it's unfortunate but we may have to live with it. Curious to know what's being overcounter and if usecounter could tweak<br>
&lt;dael> iank_: Not easily. Would have to run the scenario where not stretching items to container which is not easy. That's how I thin it's overcounting. Would need to layout twice.<br>
&lt;dael> iank_: I think way forward to investigate is look at sites and see which flexboxes have this and if they would change<br>
&lt;dael> fantasai: Is there a way to get a sample of the list?<br>
&lt;dael> iank_: Go to the issue on the chrome status page. Below the graph there will be a list of urls that triggered the counter<br>
&lt;dael> fantasai: I'd be down to check the first 20 or something and see<br>
&lt;dael> astearns: If you want to do that it would be great. Would you like to keep issue open until you do it? Or resolve?<br>
&lt;dael> fantasai: Sure, I'll need something to track.<br>
&lt;dael> fantasai: So just load these pages and look at it?<br>
&lt;dael> iank_: Yeah, so it will be...it's by origin. What I find when doing this is if you hit the home page and have some JS to query elements more or less the home page will have it.<br>
&lt;iank_> https://www.chromestatus.com/metrics/feature/timeline/popularity/4057<br>
&lt;dael> fantasai: If I find most of these don't hit a change we can revisit. If not I'll close out<br>
&lt;dael> astearns: Okay, leaving this as is<br>
&lt;dael> action fantasai look at effect this https://github.com/w3c/csswg-drafts/issues/3052#issuecomment-1226112918 would have on actual websites<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-1301496687 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 2 November 2022 23:43:19 UTC