[Bug 23809] New: [Custom]: Ability to look up information about custom elements which have been registered

https://www.w3.org/Bugs/Public/show_bug.cgi?id=23809

            Bug ID: 23809
           Summary: [Custom]: Ability to look up information about custom
                    elements which have been registered
           Product: WebAppsWG
           Version: unspecified
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Component Model
          Assignee: dglazkov@chromium.org
          Reporter: jan@quickui.org
        QA Contact: public-webapps-bugzilla@w3.org
            Blocks: 14968

In a variety of situations, it would be helpful to be able to look up
information about the custom elements which have been registered with the
browser.

For example, I've run into a number of cases where I'm debugging an app with
custom elements, and have to work in roundabout ways to determine whether or
not an element is being registered properly. For any given element name, I can
try document.createElement(name) and see whether the thing I get back has, say,
a shadow or not, but that feels hacky.

When debugging under the Polymer ShadowDOMPolyfill, it's actually been quite
helpful to be able to inspect the polyfill's CustomElements registry. A similar
service would be helpful in debugging native elements.

There are also situations where it'd be useful to have some form of reflection
to inspect a custom element type. See
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23808 for one specific case in
which a meta-element wants to be able to look up information about another
element type so that an instance of the latter may be created.

More generally, I've been considering the construction of various tools such as
visual design tools for custom elements. Again, these would generally require
some means to know which custom elements are available to the browser at the
moment.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Tuesday, 12 November 2013 19:49:29 UTC