Re: [csswg-drafts] [css-mixins] custom mixins & functions should have some access to custom properties on the calling element. How much? (#9938)

I'm starting to think we're over-thinking this and should just let all the properties come through and just shadow. There is already a problem of potentially shadowing custom property values in any rule, and typically careful naming is required to avoid this. My sense is that it doesn't seem sufficiently more problematic here to warrant a bespoke solution.

> Others have argued that all external variables should be (somehow) implicitly available.

@mirisuzanne  This seems to suggest that this behavior might be hard to implement or design. Is that the case?



-- 
GitHub Notification of comment by sorvell
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9938#issuecomment-1965658032 using your GitHub account


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

Received on Tuesday, 27 February 2024 02:04:59 UTC