customElements.getName() returns the tag name of the given custom element definition.
Currently there is no way to get the local name of a custom element without instantiating the instance and checking the localName property. This new method allows querying the customElementRegistry to discover the localName of a definition without creating an instance.
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
No milestones specified