- From: Daniel Holbert via GitHub <sysbot+gh@w3.org>
- Date: Wed, 18 Aug 2021 05:44:12 +0000
- To: public-css-archive@w3.org
> (Also none of the browsers support these keywords on min-block-size. But they parse it.) Could you elaborate on the lack-of-support? I believe we (Firefox at least) treat these keywords as `auto` in the block axis, which is what the spec calls for: https://drafts.csswg.org/css-sizing-3/#valdef-width-min-content Quoting that spec-text on what these keywords mean in the block axis (using `min-content` as an example here): # min-content # [...] for a box’s block size, unless otherwise specified, this is equivalent to its automatic size. In that spec quote, `automatic size` is just linked to the definition of `auto` here: https://drafts.csswg.org/css-sizing-3/#valdef-width-auto So: these keywords are specced to behave as `auto` in the block axis, basically. So if you're seeing these keywords not having any special behavior in the block axis, I think that's correct :) though maybe I'm misunderstanding the issue you're seeing. And also, I would expect these keywords to have the same definiteness guarantees as `auto` (at least in the block axis where they're literally equivalent... And probably also in the inline axis since sizes are typically more eagerly definite in the inline axis, I think? Though it'd probably be worth testing some inline-axis scenarios.) -- GitHub Notification of comment by dholbert Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6457#issuecomment-900828143 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 18 August 2021 05:44:14 UTC