W3C home > Mailing lists > Public > public-css-archive@w3.org > March 2017

[csswg-drafts] [css-sizing] Percentage sizing section is kind of vague

From: Christian Biesinger via GitHub <sysbot+gh@w3.org>
Date: Mon, 27 Mar 2017 21:46:44 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-217385209-1490651203-sysbot+gh@w3.org>
cbiesinger has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-sizing] Percentage sizing section is kind of vague ==
https://drafts.csswg.org/css-sizing-3/#percentage-sizing

That section is a bit vague. It currently says:

> Percentages specify sizing of a box with respect to the box’s containing block.
> 
> Although this may require an additional layout pass to re-resolve percentages in some cases, the auto, min-content, max-content, and fit-content values of min-width and min-height do not prevent the resolution of percentage sizes of the box’s contents. However, in order to prevent cyclic sizing in the general case, percentages do not otherwise resolve against indefinite sizes, and instead are treated as auto.

I actually think the text is wrong, in that sizes can only be resolved against definite sizes but the text does not specify that limitation. But beyond that:
* The text implies that max-height can affect percentage resolution of the height (if it is something like min-content), but does not specifically say so
* It seems to imply also that min-content will never prevent percentage resolution of children, but I am not sure that my reading is correct and would appreciate clarification
* It would be nice to clarify that while max-content can prevent percentage resolution of children/descendants, it never affects the value the percentage gets resolved against (that value is always the specified height). OR, if I misunderstood, it would be good to explicitly say so.

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1132 using your GitHub account
Received on Monday, 27 March 2017 21:46:50 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 19 October 2021 01:30:30 UTC