- From: Miriam Suzanne via GitHub <sysbot+gh@w3.org>
- Date: Wed, 16 Oct 2024 16:12:33 +0000
- To: public-css-archive@w3.org
Yeah, I understand concerns about proximity being heuristic and associated with scope, but: - Proximity is extremely useful for situations like this. Enforcing lower boundaries everywhere requires careful coordination across entire projects. - It's not a huge survey, but as [my quick mastodon poll](https://front-end.social/@mia/113307621867526584) isn't even close. This is something authors have been asking for since 2009 at least. Nicole Sullivan used to give talks about it. - We could look for a way to trigger it explicitly, but it requires _the same parts_ as other scoping, and is used for the same semantic purpose (components negotiating ownership). So if we did split out the syntax, it would need to part of or at least based on scoping. But I haven't actually seen any use-cases where you want one of these behaviors and don't want the other. I've only seen hand-wringing about it, and no examples of why it's not useful or should be separate. -- GitHub Notification of comment by mirisuzanne Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10795#issuecomment-2417291779 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 16 October 2024 16:12:34 UTC