Re: [csswg-drafts] [css-box-4] Longhand values of `margin-trim` allow more combinations than shorthand values (#7884)

The CSS Working Group just discussed ``[css-box-4] Longhand values of `margin-trim` allow more combinations than shorthand values``, and agreed to the following:

* `RESOLVED: Allow combination of 'block' and 'inline' keywords in 'margin-trim'`

<details><summary>The full IRC log of that discussion</summary>
&lt;fantasai> none | block | inline | [ inline-start || inline-end || block-start || block-end ]<br>
&lt;jarhar> fantasai: the current syntax of margin trim looks liek this, which doesnt very eaily allow the ability to say all of the sides<br>
&lt;fantasai> none |<br>
&lt;fantasai> [ block || inline ] |<br>
&lt;fantasai> [ block || inline-start || inline-end ] |<br>
&lt;fantasai> [ inline || block-start || block-end ] |<br>
&lt;fantasai> [ inline-start || inline-end || block-start || block-end ]<br>
&lt;jarhar> fantasai: there was a suggestion to allow all possible combinations that make any sense<br>
&lt;jarhar> fantasai: then there was tabs alternative proposal which was to change the block or inline the original syntax to a double or which would look like<br>
&lt;fantasai> none | [ block || inline] | [ inline-start || inline-end || block-start || block-end ]<br>
&lt;jarhar> fantasai: im not sure how often peoplw ant to trim 3 our of 4 sides and if they really want to they can list 3 keywords instead of 2<br>
&lt;jarhar> TabAtkins: the third keyword would be slightly longer<br>
&lt;jarhar> fantasai: i suggest we accept tabs proposal<br>
&lt;una> q+<br>
&lt;jarhar> una: i like it lets do it<br>
&lt;miriam> ack una<br>
&lt;bramus> +1<br>
&lt;jarhar> miriam: the other proposal in there about all, is that something that needs discussion?<br>
&lt;jarhar> TabAtkins: it was my suggestion, i dont care. elikas hesitation ??<br>
&lt;oriol> q+<br>
&lt;jarhar> una: i wouldnt mind having both all and block inline but if there is risk for future compat then im happy with just block inline<br>
&lt;miriam> ack oriol<br>
&lt;TabAtkins> s/??/hesitation about confusion with possible future additions makes sense to me/<br>
&lt;jarhar> oriol: are we then allowing combination of horziontal block wth inline keywords? the second thing you wrote isnt allowing those combinations?<br>
&lt;jarhar> fantasai: yeah you cant write block inline start if you wanted to do that youd have to write block start inline start block end<br>
&lt;jarhar> una: its like margin<br>
&lt;jarhar> fantasai: i think thats ok<br>
&lt;jarhar> fantasai: proposed resolution is to allow the combination of block and inline keywords<br>
&lt;jarhar> miriam: any objections to that resolution?<br>
&lt;fantasai> RESOLVED: Allow combination of 'block' and 'inline' keywords in 'margin-trim'<br>
</details>


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


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

Received on Tuesday, 11 June 2024 14:47:22 UTC