Re: [w3c/webcomponents] Is there a way to retrieve the localName from a custom element constructor? (#566)

@rniwa Okay, thanks, that's very helpful.

> CustomElementRegistry and window.customElements should be about custom elements, not builtin elements. None of existing methods do anything with builtin elements.

So a solution like the one I proposed above — representing built-ins in a registry that was separate from `customElements` — would at least meet this particular requirement, correct? That’s not to say that you'd accept that particular solution; I'm just trying to confirm my understanding of your requirement.

> WebKit doesn't have a mapping of builtin element constructor objects to local names, and we don't want to introduce one just for this API.

I don't see a way around that, although I guess also I don't see why that would be costly.

In any event, perhaps the above point is the crux of the matter: you don't see a need to invest in something like this, because you're comfortable with a solution that only works with custom elements. @domenic, meanwhile, is only willing to accept something that works with both. If that's true, maybe we are at a real impasse.

The only compromise I could envision would be if Apple and Google could agree in principle to spreading out this work over time. E.g., to use my `rootRegistry` strawman above just as an example, let's imagine that everyone thought that was a reasonable solution:

* Since Apple doesn't see a pressing need to tackle this problem, it would leave out support for a `rootRegistry` that sits above `customElements` in the hierarchy.
* Google, however, could implement it right away because they assign a higher priority to treating built-ins and custom elements equally. Perhaps Mozilla follows suit.
* Let’s assume some form of polyfill is possible.
* Eventually, if Apple feels developer interest has reached some threshold that would justify the work, they’d make the investment to implement the feature.

Would this approach (not necessarily the specific solution) work? I’m just looking for a way to resolve the impasse.

-- 
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-545991617