Brandon McConnell

@Ouskababoushka Did you install the Typed.css package itself? It won't work by simply importing via `@import 'typed';` I should probably clarify that in the readme, but I believe you'll need...

Thanks @CvdL-UM! @Manish2612 did that solve the issue you were experiencing?

@CvdL-UM I'll assign this to myself and try to get to this soon. Thanks for calling this out!

I opened a [nearly identical issue](https://github.com/w3c/csswg-drafts/issues/7881) to this earlier today that thankfully, @Loirooriol caught before I went too far down that rabbit hole. Originally, I started with the function name,...

> I think you can do this today with `:has()` but the ergonomics might not be ideal. _At least it is possible to polyfill/downgrade_ @romainmenke Thanks for your feedback! I...

Another idea to help differentiate globally set variables from locally set variables would be to implement a unique syntax unique to when you want to set a global/scoped variable. Even...

@Loirooriol Couldn't attackers do that in the console by simply using `element.value`? This would essentially work the same as that, so I think any of the same protections we have...

@Loirooriol Yeah, it's a valid concern. I think it would be worth having a larger conversation about protecting against that before implementing a feature like this. I don't think we...

@tabatkins Hi Tab, yes, sorry— I didn't call out the related issue #7866 very "loudly" in my brief, so it could easily have been missed. My apologies for that. Without...

@mirisuzanne @fantasai @LeaVerou I also think this could be confusing for nesting contexts opened within scoped contexts, like in the example below: ```css .media { /* & === .media */...