- From: Miriam Suzanne via GitHub <noreply@w3.org>
- Date: Wed, 16 Jul 2025 19:59:42 +0000
- To: public-css-archive@w3.org
> Just as a signal in the definition that it intends to take contents. Ok. It seems to me that this is also communicated by not using `@contents` anywhere in the mixin – and that could also be used as a sign to flag an error? I'm not against it strongly, just don't see much utility from it. > Edits welcome. Of course, I was just noting my initial thoughts – whoever makes the update. > Not sure what you mean by this. I was probably mis-reading. I see you've already made changes in that section, and it seems clear to me. > Definitely agreed. I'll see if there's an open issue, or open one. -- GitHub Notification of comment by mirisuzanne Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9350#issuecomment-3080140162 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 16 July 2025 19:59:43 UTC