- From: Keith Grant via GitHub <sysbot+gh@w3.org>
- Date: Mon, 12 Dec 2022 17:45:53 +0000
- To: public-css-archive@w3.org
After playing around with the Chromo prototype a bit, I'm beginning to agree the weak scoping proximity is the right call. My initial gut was the opposite: strong proximity seems to more accurately reflect what I have historically wanted in component-based design. But I think intentional use of the inner scoping bound is a good way to reproduce the effect of strong scoping, while still leaving the author with more options provided by weak scoping. In other words, if the author wants strong scoping, they can achieve it by providing all scoped components with an inner-bound container (or containers), thereby preventing outer scoped rules from ever selecting elements inside inner scopes. In my experience using component based web applications, it's uncommon for an outer component/scope to need to apply general styles on all inner components, so applying an inner bound to the scope would likely be the norm — but I like that weak scoping doesn't lock me into that and I can code it a different way when needed. Again, it feels like it provides the most flexibility to the author while still meeting the requirements. -- GitHub Notification of comment by keithjgrant Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6790#issuecomment-1346946058 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 12 December 2022 17:45:55 UTC