- From: Jen Simmons via GitHub <sysbot+gh@w3.org>
- Date: Wed, 21 Sep 2016 14:13:25 +0000
- To: public-css-archive@w3.org
I don't have a overwhelming preference. On the one hand, having something that looks broken will help authors know they should rethink their code. On the other hand, I can see this coming up in real world usecases, and having Grid return a broken result is a bad idea. It would be better for it to resolve in some kind of useable way. Maybe we want the % track to resolve to zero if it's empty. Basically — have it always act like it's `auto`. Maybe we want the % track to act like it's `minmax( backcomputethingy, auto)` — where it acts like auto if the content is making it grow beyond the competed size. But if there's not that much content / is no content, then it acts like the examples where the size is computed based on the other sizes. Basically giving us both of these, depending on whether or not there is content.   -- GitHub Notification of comment by jensimmons Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/509#issuecomment-248624719 using your GitHub account
Received on Wednesday, 21 September 2016 14:13:40 UTC