- From: Evan You via GitHub <sysbot+gh@w3.org>
- Date: Sat, 11 Mar 2023 06:24:05 +0000
- To: public-css-archive@w3.org
Some thoughts from the perspective of a framework implementor: we (Vue.js) currently simulate component-scoped styles using scope attributes (as shown in the first half of [this example](https://drafts.csswg.org/css-cascade-6/#example-463550a5)), and `@scope` would greatly simplify our implementation (as shown in the latter half of the linked example). From our perspective, we would prefer weak proximity because that is closer to how our current implementation works in practice. Users can still override specific component styles with global rules - this is a very common when using 3rd party components that you can't easily modify. I've played with some prototypes, and `@scope` being weak means we can very easily migrate to it as the underlying implementation without much compatibility concerns. I believe this is also one of the main motives of this proposal. If `@scope` ends up with strong proximity, it would make it much harder for us to consider adopting it, due to the drastic cascading priority difference from our current implementation. -- GitHub Notification of comment by yyx990803 Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6790#issuecomment-1464840665 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 11 March 2023 06:24:07 UTC