- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Fri, 21 Oct 2022 21:28:51 +0000
- To: public-css-archive@w3.org
Yup, just remember that the important part is that we care about the trees that the *styles* come from, not what trees the elements are in that actually use the styles. Then the "name inheritance" is a convenience feature, intentionally leaking names defined in one tree into descendant trees, taking metaphorical advantage of the existing info-leak that inheritance represents. > If not, I think inheritance is doing more risk than good as it breaks shadow DOM encapsulation, and it's complicated to implement without good use cases. If it's a significant complication I'm okay with dropping it and leaving the spec as is (and modifying the advice in Scoping to match up). The cases are reasonably minimal, yeah. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7916#issuecomment-1287452527 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 21 October 2022 21:28:52 UTC