- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 04 Oct 2017 23:14:47 +0000
- To: public-css-archive@w3.org
The Working Group just discussed `Flex sum < 1`, and agreed to the following resolutions: * `RESOLVED: Revert the previous resolution regarding flex sum <1 (as has already been done) and solicit dholbert's review.` <details><summary>The full IRC log of that discussion</summary> <TabAtkins> Topic: Flex sum < 1<br> <TabAtkins> GitHub: https://github.com/w3c/csswg-drafts/issues/1735#issuecomment-332671797<br> <TabAtkins> astearns: My understanding was that we had a resolution, but we had to revert it because there was a discontinutiy.<br> <TabAtkins> fantasai: Yes, we need to be continuous for a given flex item going from 0=>1, *and* for the flex container when its children do the same.<br> <TabAtkins> fantasai: Previous resolution fixed the flex item, but it created a discontinuity for the flex container.<br> <TabAtkins> fantasai: So our proposal ends up giving non-linear behavior for flex items when the sum is <1, but it's continuous.<br> <TabAtkins> astearns: Has dholbert looked at the revert?<br> <TabAtkins> TabAtkins: He hasn't commented yet, so if he's seen it he hasn't approved it.<br> <TabAtkins> astearns: So should we wait until we get feedback?<br> <TabAtkins> TabAtkins: I'd prefer to get someone invested to give positive feedback.<br> <TabAtkins> rego: I think we should accept the proposal.<br> <TabAtkins> astearns: Have you reviewed the reverted text.<br> <TabAtkins> rego: No, haven't checked the new text specifically, but I want continuity.<br> <TabAtkins> astearns: fantasai, what do you want to do?<br> <TabAtkins> fantasai: Resolve to revert to the previous text unless dholbert has opposite ideas.<br> <TabAtkins> astearns: Any objections to reverting?<br> <TabAtkins> RESOLVED: Revert the previous resolution regarding flex sum <1 (as has already been done) and solicit dholbert's review.<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1735#issuecomment-334316053 using your GitHub account
Received on Wednesday, 4 October 2017 23:14:36 UTC