[Bug 27437] New: [Custom]: Be clear about whether attached callback should be enqueued when setting prototype

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

            Bug ID: 27437
           Summary: [Custom]: Be clear about whether attached callback
                    should be enqueued when setting prototype
           Product: WebAppsWG
           Version: unspecified
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Component Model
          Assignee: dglazkov@chromium.org
          Reporter: wchen@mozilla.com
        QA Contact: public-webapps-bugzilla@w3.org
                CC: mike@w3.org, public-webapps@w3.org
            Blocks: 14968

http://w3c.github.io/webcomponents/spec/custom/#dfn-created-callback:

"The custom element prototype must be set just prior to invoking callback."

"If the created callback exists for an element, all other callbacks must not be
enqueued until after this created callback's invocation had started."

In the steps to set the custom element prototype we have:

http://w3c.github.io/webcomponents/spec/custom/#dfn-set-prototype

3.1. "Enqueue attached callback for ELEMENT"

There is instruction to enqueue an attached callback and instruction to not
enqueue the attached callback because it happens before invoking the created
callback.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Received on Wednesday, 26 November 2014 02:11:28 UTC