- From: Mats Palmgren via GitHub <sysbot+gh@w3.org>
- Date: Sun, 27 Nov 2016 02:20:59 +0000
- To: public-css-archive@w3.org
> I do think that the stretching effectively overrides the automatic minimum. OK, fair enough -- I think you are saying that it's desirable if it does that. However, I think your statement is a bit to general - it's only the min-content size part of the automatic minimum size it should override. If we should shrink below a "transferred size" can be discussed, but let's resolve that bit in https://github.com/w3c/csswg-drafts/issues/767 (The "specified size" part of automatic minimum size never applies together with stretching because stretching doesn't occur when there is a definite specified size.) So, here's what I propose to resolve this issue: Firefox changes its stretching to shrink items below their min-content size. Chrome implements Grid ยง6.6 clamping (https://bugs.chromium.org/p/chromium/issues/detail?id=666940) Then I think we would have identical layout for these tests. I think that requires minimal spec changes: no Grid spec changes at all. A minor amendment to CSS Align to say that stretching may shrink the alignment subject so that its content size is below its min-content size (still not below any non-`auto` `min-width/height` of course). How does that sound? -- GitHub Notification of comment by MatsPalmgren Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/283#issuecomment-263098171 using your GitHub account
Received on Sunday, 27 November 2016 02:21:05 UTC