- From: Matthew Phillips via GitHub <sysbot+gh@w3.org>
- Date: Thu, 16 Mar 2023 13:57:31 +0000
- To: public-css-archive@w3.org
I have a hard time answering this question because I'm having trouble understanding how tooling can leverage this proposal in general. For example, a component-oriented framework might want to use this feature instead of hashed class names to scope a component. So if you have a component like this:
```html
<div class="one"><span class="inner"></span></div>
```
You might naively compile scoped CSS to:
```css
@scope (.one) {
.inner { color: darkmagenta; }
}
```
But then if you have a second component that uses the same `one` class name:
```html
<div class="one"><input class="inner"></div>
```
Now you have mistakenly applied the first component's styles to this component. So you haven't gotten rid of the need for hashing. Am I misunderstanding something?
--
GitHub Notification of comment by matthewp
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6790#issuecomment-1472025187 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 16 March 2023 13:57:33 UTC