W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2014

[Bug 25142] New: [Custom]: Missing created callback should not prevent other callbacks from being enqueued.

From: <bugzilla@jessica.w3.org>
Date: Mon, 24 Mar 2014 19:22:01 +0000
To: public-webapps@w3.org
Message-ID: <bug-25142-2927@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25142

            Bug ID: 25142
           Summary: [Custom]: Missing created callback should not prevent
                    other callbacks from being enqueued.
           Product: WebAppsWG
           Version: unspecified
          Hardware: All
               URL: http://w3c.github.io/webcomponents/spec/custom/#types-
                    of-callbacks
                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

In the description of the created callback the spec currently says:

"All other callbacks must not be enqueued until after the created callback's
invocation had started."

It's not very clear what should happen when there is no created callback
transferred from the prototype. The way it's currently worded, there is no
callback to invoke and no other callbacks would be enqueued. This seems like
the wrong behavior to me.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Monday, 24 March 2014 19:22:02 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:14:22 UTC