Re: [csswg-drafts] [css-grid] Reconsider the meaning of 1fr

The Working Group just discussed `Reconsider the meaning of 1fr`, and agreed to the following resolutions:

* `RESOLVED: Close issue #1777 no change`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: Reconsider the meaning of 1fr<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/1777#issuecomment-332683990<br>
&lt;dael> astearns: There's a proposal TabAtkins summerized that was from fantasai apperently...?<br>
&lt;dael> fantasai: That's a related issue. There's a problem which is unintuitive and flexbox has same problem. It's interaction of implied min size and overflow auto or scroll. What prompted this bug was running into that combo.<br>
&lt;dael> fantasai: Having discussed with jensimmons it seems we don't want to change meaning of 1fr. I propose we close the 1fr issue no change and maybe discuss ways to make the behavior of overflow auto or scroll more intuitive.<br>
&lt;dael> fantasai: It's a completely seperate framing of problem. I'd suggest first close reconsidering meaning of fr.<br>
&lt;dael> astearns: Is there a seperate issue on overflow interp?<br>
&lt;dael> fantasai: We'd need to open. We oculd change/re-title issue, but I'd liek a resolution to not change 1fr<br>
&lt;dael> astearns: Manuel or sergio have you had a chance to look?<br>
&lt;dael> rego: I think that's fine. I didn't check this comment, but I think it's fine if we don't change. We raised it because people were confused, but prob not a good idea to change.<br>
&lt;dael> astearns: You're fine closing no change?<br>
&lt;dael> rego: Yes.<br>
&lt;dael> astearns: Other opinions?<br>
&lt;dael> jensimmons: I dropped a link at the bottom where Dave Rupert wrote a good blog post explaining hte frustrations. I don't think changing 1fr is a good way to go. I sat and thought about this and the way 1fr works now is really good. I do think we should see what else we can do to help authors out becides education.<br>
&lt;dael> jensimmons: Do something around overflow or add something else to grid to solve this, but I don't think changing 1fr or changing behavior between rows and columns is good. Keep it the same, keep it symmetrical, see what else we can do for authors.<br>
&lt;dael> astearns: Is what fantasai spoke about with overflow does that address Dave's frustrations?<br>
&lt;dael> jensimmons: I don't think he has the best solution, but he's talking about exactly those problems. He has one way to solve it and there are other ways to solve it that we list in the issue like min/max 0 to 1fr would work. Authors don't know that because they don't understand what's a replaced element, but we can teach them that.<br>
&lt;dael> astearns: I'm hearing consensus to close no change and then continue discussion on how to explain how overflow works with grid. Objections?<br>
&lt;dael> RESOLVED: Close issue #1777 no change<br>
&lt;dael> fantasai: We'll open a new issue starting with the blog post.<br>
&lt;dael> astearns: Is that you fantasai or jensimmons?<br>
&lt;dael> fantasai: I can do it.<br>
&lt;dael> jensimmons: I'm happyt o comment, but fantasai will do a better job explaining.<br>
</details>


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

Received on Wednesday, 11 October 2017 16:18:58 UTC