- From: Romain Menke via GitHub <noreply@w3.org>
- Date: Thu, 30 Apr 2026 06:17:34 +0000
- To: public-css-archive@w3.org
> We want to build a feature-rich CSS library where users can import a specific component (e.g., a button or popup tooltip) without manually managing its sub-dependencies or importing the entire library. I fully agree with this. But I don't see why you aren't using `@import` in each component stylesheet to describe the dependencies of that stylesheet. What is stopping you from doing that? Why leave it up to users of your library to figure out which dependencies there are for each thing they want to use? My guess is that the issue you encounter there is the real issue and what we should focus on. Is this about naming clashes? -- GitHub Notification of comment by romainmenke Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6130#issuecomment-4350126550 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 30 April 2026 06:17:35 UTC