Re: [csswg-drafts] [css-backgrounds-4] Can you chain `border-area` and `text` in `background-clip`? (#10696)

The CSS Working Group just discussed ``[css-backgrounds-4] Can you chain `border-area` and `text` in `background-clip`?``, and agreed to the following:

* ``RESOLVED: Add `border-area || text` to the background-clip syntax``

<details><summary>The full IRC log of that discussion</summary>
&lt;TabAtkins> fantasai: suggestion to combine some of the background-clip areas, particularly 'text' and 'border-area'<br>
&lt;fantasai> https://github.com/w3c/csswg-drafts/issues/10696#issuecomment-2284375965<br>
&lt;TabAtkins> fantasai: this seems fine to me<br>
&lt;TabAtkins> fantasai: also a suggestion to allow arbitrary combos, don't think we shoudl do that. not worth it for almost all of the combos.<br>
&lt;TabAtkins> fantasai: we can enable particular combos as needed; currently i think text and border-area is the only reasonable one<br>
&lt;TabAtkins> TabAtkins: okay, it's a combination of the two areas, i thought it was gonna be an intersection<br>
&lt;dbaron> does this preclude doing intersections later?<br>
&lt;TabAtkins> smfr: yeah it saves you from ahving to do two backgrounds if they'd be the same<br>
&lt;TabAtkins> fantasai: i think if you want an intersection we should have a specific syntax for it<br>
&lt;fantasai> TabAtkins: once you get there, ordering dependency matters<br>
&lt;fantasai> TabAtkins: interesting feature, but requires justification and development<br>
&lt;dbaron> (clipping background to the text that is inside the &lt;*-box> seems like not too unusual a request<br>
&lt;TabAtkins> astearns: so proposal is to add `border-area || text` as a valid value<br>
&lt;TabAtkins> astearns: no prejudice against more changes in the future<br>
&lt;TabAtkins> astearns: objections?<br>
&lt;TabAtkins> RESOLVED: Add `border-area || text` to the background-clip syntax<br>
</details>


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


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

Received on Thursday, 7 November 2024 00:57:15 UTC