- From: Michael Warren <notifications@github.com>
- Date: Tue, 01 Aug 2023 05:51:26 -0700
- To: WICG/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 1 August 2023 12:51:31 UTC
> Respectfully, I think that proposal falls short in a number of ways: Just wanted to add a comment here on the topic of these custom enhancements/attributes to say that I think that scoping should be a first-party concern whenever the element in question has a "canonical name". I think that the global nature of the custom element registry is coming to bear as a problem rather than the desired end state, and as such I think that we should consider scoping as a first concern with any new feature where defining the thing starts with some name that must be unique. IMO any feature like custom elements or custom behaviors/enhancements should have the ability to be scoped to a particular element/collection so that third party libraries can safely declare these without worrying about conflicts in consuming applications. -- Reply to this email directly or view it on GitHub: https://github.com/WICG/webcomponents/issues/1018#issuecomment-1660250056 You are receiving this because you are subscribed to this thread. Message ID: <WICG/webcomponents/issues/1018/1660250056@github.com>
Received on Tuesday, 1 August 2023 12:51:31 UTC