Re: [csswg-drafts] [css-backgrounds-4] default background-origin for `border-area` in shorthand (#11167)

The CSS Working Group just discussed ``[css-backgrounds-4] default background-origin for `border-area` in shorthand``, and agreed to the following:

* `RESOLVED: Using 'border-area' in the background shorthand (and omitting origin) defaults the origin to border-box`

<details><summary>The full IRC log of that discussion</summary>
&lt;TabAtkins> fantasai: in the bg shorthand if you specify a single keyword like 'border-box', it sets both clip and origin to that keyword<br>
&lt;TabAtkins> fantasai: but 'border-area' keyword is only valid for clip, not origin<br>
&lt;TabAtkins> fantasai: want to clarify that in that case, origin defaults to border-box<br>
&lt;TabAtkins> +1 to this from me<br>
&lt;kizu> +1, makes sense<br>
&lt;oriol> +1<br>
&lt;TabAtkins> Rossen0: objections?<br>
&lt;fantasai> background: ... border-area;<br>
&lt;emilio> A bit unfortunate that it's different from background: ...; background-clip: border-area<br>
&lt;emilio> But yeah<br>
&lt;TabAtkins> RESOLVED: Using 'border-area' in the background shorthand (and omitting origin) defaults the origin to border-box<br>
&lt;TabAtkins> fantasai: second, do we want some way to make things default if you specify the longhand?<br>
&lt;TabAtkins> fantasai: argument for, it's unfortuante/confusing to get it set to the "wrong" value<br>
&lt;TabAtkins> fantasai: argument against, it's not something we're currnetly doing<br>
&lt;TabAtkins> Rossen0: okay, will leave that part of the discussion<br>
&lt;fantasai> for other values of background-clip (though maybe we should have)<br>
</details>


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


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

Received on Wednesday, 13 November 2024 18:00:43 UTC