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

> I really liked the idea to recall the arguments via arg(--foo)

That could be a piece of the puzzle but it seems like maybe there's a problem with the fact that we just have use `:` for assignment. For example, it's not uncommon currently to define "private" custom properties by convention (`--_private`). That always feels weird, but do we leverage it here?

What does that mean to define a value inside a mixin?

```css
@apply --bar(--b: 5px;) {
  outline-width: arg(--b); /* 5px? */
  border-width: var(--b); /* 2px  or requires `using` */
  padding-left: var(--a); /* is this anything? */
}

@mixin --foo(
  --a: 1px;
) {
  --b: 2px; /* is this always a custom property? */
  div {
    @apply --bar();
  }
}

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


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

Received on Friday, 23 February 2024 19:50:18 UTC