[Bug 21641] New: [Custom]: Consider firing insertedCallback when Custom Element is upgraded when already inserted in dom.

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

            Bug ID: 21641
           Summary: [Custom]: Consider firing insertedCallback when Custom
                    Element is upgraded when already inserted in dom.
    Classification: Unclassified
           Product: WebAppsWG
           Version: unspecified
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Component Model
          Assignee: dglazkov@chromium.org
          Reporter: sorvell@chromium.org
        QA Contact: public-webapps-bugzilla@w3.org
            Blocks: 14968

I believe there is now agreement that the spec should include
inserted/removedCallbacks that are fired when a custom element is
inserted/removed from dom.

We may want to fire the insertedCallback when a custom element is upgraded when
already in dom.

Assume, for example, a developer wants to add event listeners when a custom
element is inserted. If we do not call inserted on upgrade, the developer is
forced to write boilerplate code in readyCallback that checks if the element is
already in dom and calls the same code as the insertedCallback would.

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

Received on Tuesday, 9 April 2013 19:17:21 UTC