- From: Bramus! via GitHub <sysbot+gh@w3.org>
- Date: Wed, 31 Aug 2022 12:45:18 +0000
- To: public-css-archive@w3.org
> Now I finally understand what you meant with that. We should give this rule a general name so that it can be extended in the future and restrict it to image manipulations for now. Yes, that’s what I meant by that. Was purely looking at the “shape” of how it was defined. But as @tabatkins pointed out that’s because it _“follows standard CSS syntactic patterns”_ – Same can be said for other at-rules such as `@font-face`, `@scroll-timeline` (RIP), … The listed examples reminded me of them, mainly because many of the descriptors have a directly matching property. This was a wrong path to follow. Generalizing also doesn’t seem a good idea the more I think about it, especially if an author would want to feature detect this using [`at-rule()`](https://github.com/w3c/csswg-drafts/issues/2463#issuecomment-1016720310). tl;dr disregard my mentions of mixins -- GitHub Notification of comment by bramus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6807#issuecomment-1232890863 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 31 August 2022 12:45:20 UTC