Re: [csswg-drafts] [css-rhythm-1] Add `content-box` to `block-step-insert` so authors can have content grow instead of adding space (#10486)

The CSS Working Group just discussed ``[css-rhythm-1] Add `content-box` to `block-step-insert` so authors can have content grow instead of adding space``, and agreed to the following:

* `RESOLVED: Switch block-step-insert margin and padding values to margin-box | padding-box and add content-box, with attention to impact on aspect-ratio`

<details><summary>The full IRC log of that discussion</summary>
&lt;chrishtr> fantasai: this is an issue from jen where she pointed out that block-step-insert has two values: margin and padding. pointed out use cases for content.<br>
&lt;fantasai> block-step-insert: margin | padding<br>
&lt;chrishtr> fantasai: these names don't align with other naming<br>
&lt;fantasai> block-step-insert: margin-box | padding-box | content-box<br>
&lt;florian> s/us introducing more longhands/us introducing more longhands from the get go even when they're not needed yet when we can imagine needing them for a later extension of a feature<br>
&lt;chrishtr> fantasai: propose to change to add the -box suffix and also include the content variant<br>
&lt;florian> +1<br>
&lt;chrishtr> rossen: sounds reasonable, don't know why we didn't do content before<br>
&lt;chrishtr> fantasai: just because it's an early spec, probably accidental<br>
&lt;chrishtr> lwalrlow: has any implementation shipped?<br>
&lt;chrishtr> fantasai: no<br>
&lt;chrishtr> lwarlow: cool, then sounds good<br>
&lt;chrishtr> ikilpatrick: does setting this property effectively override aspect-ratio for an image?<br>
&lt;chrishtr> fantasai: yes. but maybe it shouldn't, good point?<br>
&lt;chrishtr> ikilpatrick: if it doesn't override aspect-ratio, how does it work with the original use case mentioned?<br>
&lt;chrishtr> fantasai: if you set a fixed width it's like setting a height which affects aspect-ratio<br>
&lt;chrishtr> fantasai: but if width were auto then maybe it makes sense for it to pass through<br>
&lt;chrishtr> ikilpatrick: stretch is also involved<br>
&lt;chrishtr> ikilpatrick: for grid and flex<br>
&lt;chrishtr> fantasai: currently this property doesn't apply to flex or grid, but might happen in the future<br>
&lt;chrishtr> ikilpatrick: concerned about all sorts of  complications for replaced elements<br>
&lt;chrishtr> fantasai: should probably enter the algorithm in a similar place to min-height and min-width<br>
&lt;chrishtr> ikilpatrick: Just needs to be documented explicitly in the spec as to where it is in the order of operations. probably twice, similar to aspect-ratio<br>
&lt;chrishtr> fantasai: should be doable for block flow, but flex and grid could be more complicated<br>
&lt;chrishtr> ikilpatrick: more concerned about replaced elements than flex or gird<br>
&lt;chrishtr> fantasai: will write up proposed edits and send to you (ikilpatrick) for review<br>
&lt;chrishtr> rossen: are we good to go for the proposed resolution?<br>
&lt;Rossen7> q?<br>
&lt;chrishtr> fantasai: yes, just need to be careful about replaced element<br>
&lt;fantasai> RESOLVED: Switch block-step-insert margin and padding values to margin-box | padding-box and add content-box, with attention to impact on aspect-ratio<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10486#issuecomment-2192115032 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 26 June 2024 16:26:00 UTC