- From: fantasai via GitHub <sysbot+gh@w3.org>
- Date: Thu, 23 Feb 2017 20:50:57 +0000
- To: public-css-archive@w3.org
It does seem like in that testcase, Gecko is starting out the table with the content-based size, and then taking the remaining space up to the containing block width, distributing that space to the cells one by one to fulfill their desired percentage of the table (assuming 100% fits the containing block exactly) and giving up once all the excess space has been distributed. That's a fun algorithm, but it doesn't seem like a case of infinite max-content width. :) -- GitHub Notification of comment by fantasai Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1046#issuecomment-282116983 using your GitHub account
Received on Thursday, 23 February 2017 20:51:04 UTC