- From: Miriam Suzanne via GitHub <sysbot+gh@w3.org>
- Date: Thu, 20 Feb 2025 20:22:19 +0000
- To: public-css-archive@w3.org
Yes, stepping back from the specifics of shadow-dom, this seems like an identical issue to handling layer names from third-party tools. The tool might do layering internally, and those layer names may not match the names used in my project. The current solution is that we can wrap the tool layers into any layer of our own, when importing: ```css @import 'tool.css' layer(my-layer-name); ``` That works great as long as we're dealing with an entire import as a single layer. Where it gets complicated is if we want to rename individual layers from the import. The `@sheet` rule could help us with that, as long as the tool provides distinct sheets for us to import into distinct layers. If we need a solution that's more direct (without going through sheets) it still seems to me like on-import is the right time to handle that renaming. I'm a bit skeptical about creating arbitrary aliases at any point in the document, especially inside selectors. -- GitHub Notification of comment by mirisuzanne Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10091#issuecomment-2672597866 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 20 February 2025 20:22:20 UTC