Re: [csswg-drafts] [css-flexbox-1] Intrinsic sizing algorithm seems to produce 0 for many common cases

The CSS Working Group just discussed `Intrinsic sizing algorithm seems to produce 0 for many common cases`, and agreed to the following resolutions:

* `RESOLVED: Change the spec to treat width and height as input for the max content size`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: Intrinsic sizing algorithm seems to produce 0 for many common cases<br>
&lt;dael> Github topic: https://github.com/w3c/csswg-drafts/issues/1435<br>
&lt;fantasai> Options: https://github.com/w3c/csswg-drafts/issues/1435#issuecomment-321098718<br>
&lt;dael> fantasai: There is an issue filed by dholbert pointing out max-content of a flex container is only defined by max content size of its content and flex-basis isn't taken into account. Empty elements in flex with a basis it shrinks to 0.<br>
&lt;dael> fantasai: dholbert pointed out this is unintuitive. We did give it a size<br>
&lt;dael> fantasai: We have options here. No one has a good arguement for one over another. We need WG or community opinion. We could do nothing and leave as-is. We could treat specified width or height as a size that needs honor and ignore flex-basis. WE could do flex-basis and ignore width and height. And this would all be inflated by max-content.<br>
&lt;dael> fantasai: If I was going to pick randomly I would say use width and height but not flex-basis<br>
&lt;dael> Bert: Sounds like it's not a serious problem, but I may be misreading. Any opinions?<br>
&lt;dael> gregwhitworth: I'd agree with width and height but not flex-basis. My only worry is, I don't expect people to hit this on web but they prob wouldn't know they have empty flex.<br>
&lt;dael> gregwhitworth: Any compat issues?<br>
&lt;dael> rachelandrew: As an author it's not an issue I"ve seen.<br>
&lt;dael> rachelandrew: I'd prob agree width/height not flex-basis makes sense.<br>
&lt;dael> Bert: That's one in support. Other opinions?<br>
&lt;dael> Bert: Other options...flex-basis as well as width/height and take the max, they are less desireable. Did ne not want to discuss those?<br>
&lt;dael> fantasai: flex-basis is a start place for flexing, it's an input. Width and height are set. In that case you're setting something explicit and everywhere else in CSS we take that.<br>
&lt;dael> Bert: Anybody want to argue in favor of flex-basis or max of that and width?<br>
&lt;dael> Bert: Maybe we drop those.<br>
&lt;dael> Bert: So only no change or look at width/height<br>
&lt;myles> present+: myles<br>
&lt;dael> Florian: Sounds like a good change, but is anyone rushing to impl?<br>
&lt;dael> fantasai: I'm not sure but dholbert is planning to look at flex box.<br>
&lt;dael> gregwhitworth: Looking at the test cae we have interop. It's a worthwhile change, we should make it.<br>
&lt;dael> Bert: Okay, they we need buy in from more impl.<br>
&lt;dael> Florian: We have 2 at least. That's a good start.<br>
&lt;dael> Bert: Is TabAtkins on?<br>
&lt;dael> fantasai: He's just IRC.<br>
&lt;bradk> Is there existing content that depends on current interop behavior?<br>
&lt;dael> Bert: I'm hearing some support for looking at width/height but not flex-basis which is a change in spec.<br>
&lt;dael> fantasai: Yes.<br>
&lt;dael> Bert: Do we put that up? Change the spec to treat width and height as input for the max content size<br>
&lt;dael> Bert: Who is in favor, who is against?<br>
&lt;dael> Florian: In favor<br>
&lt;rachelandrew> +1<br>
&lt;dael> Bert: I only hear in favor.<br>
&lt;dael> RESOLVED: Change the spec to treat width and height as input for the max content size<br>
&lt;dael> Bert: fantasai will you write text? or TabAtkins ?<br>
&lt;dael> Bert: Whose action?<br>
&lt;TabAtkins> We'll take care of it, don't worry<br>
&lt;dael> fantasai: We'll do it, don't worry.<br>
&lt;dbaron> I guess I'm surprised they weren't already an input to the max-content contribution, given that they're an input for other layout modes.<br>
&lt;TabAtkins> As long as it shows up in the issue<br>
</details>


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

Received on Wednesday, 23 August 2017 16:17:06 UTC