Re: [WICG/webcomponents] [Scoped registry] Clarify relationship with shadow roots (PR #965)

@nolanlawson commented on this pull request.



> @@ -119,6 +121,23 @@ As a result, it must limit constructors by default to only looking up registrati
 
 This poses a limitation for authors trying to use the constructor to create new elements associated to scoped registries but not registered as global. More flexibility can be analyzed post MVP, for now, a user-land abstraction can help by keeping track of the constructor and its respective registry.
 
+### Note on light DOM custom elements
+
+Custom elements that use light DOM (i.e. that don't call `this.attachShadow()`) may be scoped, but they must be scoped within a shadow root. For example:

I added this section to answer a question that may pop into people's heads (it certainly popped into mine), which is: "Wait, this proposal doesn't work for light-DOM-using web components?"

I'm trying to demonstrate that light-DOM-using components are perfectly compatible with this proposal, although maybe there's a better way to phrase this.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/WICG/webcomponents/pull/965#discussion_r942942116
You are receiving this because you are subscribed to this thread.

Message ID: <WICG/webcomponents/pull/965/review/1068982238@github.com>