- From: Rachel Andrew via GitHub <sysbot+gh@w3.org>
- Date: Wed, 13 Sep 2017 03:32:39 +0000
- To: public-css-archive@w3.org
I think that the expectation here from authors is different when it comes to rows vs. columns. The behaviour with regard to columns seems to make sense to people when it is explained. For example, in workshops I create a 6 column grid, intending to position items. Until I do they are all auto-placed into tracks and the content forces a track wider than it being one sixth of the available space. Someone will invariably notice that one of the tracks is wider and ask if these are not supposed to be equal, but the explanation seems to make sense to people. However I can see why this rows example in this issue would be confusing to people, and I think that @FremyCompany has a reasonable suggestion there. I think changing how fr behaves for columns might be more confusing to people and is definitely a bigger change that might cause issues with existing layouts. I'm assuming there that more people are going to be using 1fr column-wise than are row-wise and are just relying on a bare `1fr` etc. not using minmax. -- GitHub Notification of comment by rachelandrew Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1777#issuecomment-329049081 using your GitHub account
Received on Wednesday, 13 September 2017 03:32:33 UTC