- From: fantasai via GitHub <sysbot+gh@w3.org>
- Date: Mon, 06 Nov 2017 21:47:26 +0000
- To: public-css-archive@w3.org
Adjusting description back to focus on the testcase that was initially posted; there's definitely a bunch of bugs in image sizing, but wanted to discuss specifically [this testcase](data:text/html;charset=utf-8;base64,PCFET0NUWVBFIGh0bWw%2BDQo8c3R5bGU%2BDQogZGl2IHsgZGlzcGxheTogZmxleDsgYm9yZGVyOiBzb2xpZDsgd2lkdGg6IDUwJTsgfQ0KIHAgeyBtYXJnaW46IDJweDsgYmFja2dyb3VuZDogc2lsdmVyOyBmbGV4OiAxOyB0ZXh0LWFsaWduOiBjZW50ZXI7IH0NCjwvc3R5bGU%2BDQo8ZGl2Pg0KIDxpbWcgc3JjPSJodHRwczovL3BsYWNlaG9sZGl0LmltZ2l4Lm5ldC9%2BdGV4dD90eHRzaXplPTMzJnR4dD0zNTAlQzMlOTcxNTAmdz0zNTAmaD0xNTAiPg0KIDxwPkJCQkJCQg0KIDxwPkMgQyBDDQo8L2Rpdj4%3D) which shows some very interesting non-conforming behavior in Firefox. Basically what's happening is that the flex items shrink down in different stages. First of course all the excess space gets eaten up, and then the items shrink down to their min-content sizes (triggering wrapping at the spaces in item C). Then, however, instead of flooring the items at that point, Firefox starts to shrink the image. It seems to have a two-stage concept of the min-content floor. I don't know how it's doing this, but it seems rather nice, so might be worth discussing if we want to adopt it somehow. -- GitHub Notification of comment by fantasai Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1322#issuecomment-342298411 using your GitHub account
Received on Monday, 6 November 2017 21:47:33 UTC