- From: Sebastian Zartner via GitHub <sysbot+gh@w3.org>
- Date: Sun, 27 Aug 2023 00:21:30 +0000
- To: public-css-archive@w3.org
> And I'd rather prefer a general image manipulation solution than adding that functionality to yet another specific type of image.
Thinking more about this, there are cases in which image manipulation may actually not be the right solution. This depends on whether the actual rendering size can be considered within `@image` for features like repetition, sizing and positioning.
If `@image` is _not_ context aware, we could solve those use cases differently. Maybe in combination with #9183 we could introduce new `border-image-*` properties (without `source-`), so you could manipulate the images of the different regions.
When then combining this with multi-layer support (#8802), borders like in https://github.com/w3c/csswg-drafts/issues/9183#issuecomment-1680606278 could then be created like this:
```css
border-image-source:
url('corner.svg') url('frame-decor.svg') none,
linear-gradient(90deg, #bf9875, #604b38, #bf9875) image(#bf9875);
border-image-repeat: no-repeat;
```
Sebastian
--
GitHub Notification of comment by SebastianZ
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7777#issuecomment-1694530424 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 27 August 2023 00:21:33 UTC