- From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
- Date: Tue, 30 Jan 2018 13:47:44 +0000
- To: public-css-archive@w3.org
Are you referring to this part of the spec? > Putting a box in an orthogonal flow can result in the opposite: for the box’s available block space to be definite, but its available inline space to be indefinite. In such cases a percentage of the containing block’s inline size cannot be defined, and inline axis computations cannot be resolved. In these cases, [...] Given that what we do "in these cases" does take `max-height` (of the scrollport) into account, then yes, it would make a lot of sense that deciding whether or not we are "in these cases" also takes `max-height` (of the parent) into account. As far as Implementations go, we already have two (Blink and Webkit) passing this. I just made this test case to support this claim: https://github.com/w3c/web-platform-tests/pull/9255 Whether they count as separate or not I am not sure, but 7.3.1 is generally not fully inter-operable or spec compliant anyway (as evidenced by [the test results of available-size-001 through -010](https://test.csswg.org/harness/results/css-writing-modes-3_dev/grouped/section/7.3.1/)), so bug fixes will be needed, and this can be fixed along the way as necessary since it is related. -- GitHub Notification of comment by frivoal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2239#issuecomment-361597992 using your GitHub account
Received on Tuesday, 30 January 2018 13:48:17 UTC