- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Fri, 15 Apr 2022 23:07:26 +0000
- To: public-houdini-archive@w3.org
I elaborated a bit more on this in the spec, now. The big point is just that (a) if the custom property is part of the component's public API, then the name is *already* page-global in practice (it can be set on any shadow-inclusive ancestor to pass to the component, and might be visible to any shadow-inclusive descendant), and (b) if the custom property is purely internal to the component, then you already want to uniquify the name to prevent it being accidentally set to nonsense values by the outer page using it for some other purpose. Registration just follows these principles - you either want the registration global as well, or you want to uniquify the name anyway so the registration being global doesn't matter. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/939#issuecomment-1100461536 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 15 April 2022 23:07:27 UTC