- From: Mason Freed <notifications@github.com>
- Date: Wed, 08 Apr 2020 09:51:03 -0700
- To: w3c/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 8 April 2020 16:51:16 UTC
@annevk: > custom elements have a 1:1 mapping, builtins do not. What kind of API do you envision? > how would a global API for both builtin and custom elements work for scoped registries? Or are scoped registries not something Google-at-large is advocating for? I agree that this isn't straightforward. For scoped registries, since they're scoped to the shadow root, I would think that whatever API we develop for builtins should "just work" there also. But I suppose that depends on the details of the API. Anyway, since we're okay moving ahead without support for builtins, we can punt these questions until later. I should point out that "Google-at-large" is a big place with differing opinions. @rniwa: > Given there have been no concrete use case presented for retrieving builtin elements' name given their constructors, I don't think supporting builtin elements make sense. Ok. We are ok moving ahead without builtin support for now, given the strong developer demand for this feature. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/webcomponents/issues/566#issuecomment-611070151
Received on Wednesday, 8 April 2020 16:51:16 UTC