- From: jsnkuhn via GitHub <sysbot+gh@w3.org>
- Date: Mon, 24 Mar 2025 23:27:46 +0000
- To: public-css-archive@w3.org
`background-clip: text;` and `background-clip: border-area;` are incredibly illogical properties for covering both of there use cases. These properties are clearly hacks of background layers that have somehow been built directly into CSS. No one who doesn't already know that these properties exist would think that changing the `color` or `border-color` to transparent and then using a clipped background layer as fill would be the native CSS way to fill text or a border with an image. Borders should appear on the border layer. Devs shouldn't have to potentially manage multiple background images to "fake" a border. The actual logical things that I've seen people who are new to CSS write are for gradient borders and text are: ```css color: linear-gradient(); border: solid 3px linear-gradient(); ``` Personally, I still think that `border-image` is salvageable for this. Potentially adding some sort of keyword to switch modes into having `border-image` just clip a source-image to the border-area would making it work well for this use case (outset would have t e disabled I guess?). What this would lose from `background-clip: border-area` is the ability to layer multiple images. This could be restored with the @image proposal. Or could some sort of `border-fill` with the same options as image fill from the stroke-fill spec -- GitHub Notification of comment by jsnkuhn Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11974#issuecomment-2749620669 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 24 March 2025 23:27:47 UTC