- From: Amelia Bellamy-Royds via GitHub <sysbot+gh@w3.org>
- Date: Thu, 30 Apr 2020 21:05:09 +0000
- To: public-css-archive@w3.org
From the discussion, today, I think it's worth listing out our use cases / horror cases & work out requirements from them. Some examples (which we can debate about how important they are): Use case: 3rd party library ships both essential styles for components (e.g., show/hide), and also default theming styles. They want to make it easy for authors to declare styles that override the themes, but not the essentials. Use case: Web page author is importing/linking multiple 3rd-party stylesheets (resets, components, basic themes), and wants to organize them by priority without needing to edit the CSS content of those files. Use case: A website build system that concatenates multiple stylesheets for portability/performance reasons but still wants to preserve the custom origin feature. Horror case: Multiple 3rd-party components declare origins using some sort of global namespace that conflicts in a way the website author can't control. -- GitHub Notification of comment by AmeliaBR Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4969#issuecomment-622111454 using your GitHub account
Received on Thursday, 30 April 2020 21:05:10 UTC