- From: Miriam Suzanne via GitHub <sysbot+gh@w3.org>
- Date: Fri, 12 Nov 2021 18:54:07 +0000
- To: public-css-archive@w3.org
It doesn't seem to me that there is a universally *right* choice for this. In most of my CSS use-cases, I would want to define boundaries that are part of the scope (inclusive - also used by Vue), but it's also clear the exclusive approach makes more sense with some component-nesting cases. I hope we don't end up supporting one over the other. We need the choice available for authors to express both I like the fact that exclusive boundaries leave that choice open to an extent (via `boundary > *` selectors), but I think we might want some more explicit way of expressing that choice. -- GitHub Notification of comment by mirisuzanne Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6577#issuecomment-967342224 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 12 November 2021 18:54:09 UTC