- From: Anne van Kesteren via GitHub <sysbot+gh@w3.org>
- Date: Tue, 18 Jun 2024 08:49:43 +0000
- To: public-css-archive@w3.org
Couple things: 1. We should try to solve this problem for CSS naming generally. It's come up for `@font-face` and other features before and I don't think we have a general solution. Designing solutions for each feature independently seems quite bad. I hope @tabatkins and @fantasai can help out here. 2. Exposing names by default very much goes against encapsulation and is not acceptable. Exposing names always needs to be opt-in. 3. Opting into exposing names globally also seems fraught. That would violate the encapsulation of the encompassing shadow tree. It re-exposing names exposed to it seems reasonable, but that would only go one level up again. -- GitHub Notification of comment by annevk Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10145#issuecomment-2175556049 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 18 June 2024 08:49:44 UTC