W3C home > Mailing lists > Public > public-webapps-bugzilla@w3.org > November 2012

[Bug 20189] New: [Custom]: Provide an event that signals when all custom elements in static source are ready/upgraded

From: <bugzilla@jessica.w3.org>
Date: Fri, 30 Nov 2012 20:03:44 +0000
To: public-webapps-bugzilla@w3.org
Message-ID: <bug-20189-2532@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20189

            Bug ID: 20189
           Summary: [Custom]: Provide an event that signals when all
                    custom elements in static source are ready/upgraded
    Classification: Unclassified
           Product: WebAppsWG
           Version: unspecified
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Component Model
          Assignee: dglazkov@chromium.org
          Reporter: danieljb2@gmail.com
        QA Contact: public-webapps-bugzilla@w3.org
            Blocks: 14968

When using many different custom elements on a page, it quickly becomes
tiresome to have to listen for granular-upgrade bubbling for each custom
element on the page and filter for the nodes you may want to interact with.

While granular upgrade events are useful, a great many use-cases would benefit
from something like a "DOMComponentsUpgraded" event. Such an event would notify
the developer when all custom elements in the static source of the page have
finished their upgrade cycle and are ready for manipulation. Think of it as the
DOMContentLoaded for custom elements.

Thoughts?

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Friday, 30 November 2012 20:03:48 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 30 November 2012 20:03:48 GMT