W3C home > Mailing lists > Public > www-dom@w3.org > January to March 2013

[Bug 21427] New: Futures: use thenable

From: <bugzilla@jessica.w3.org>
Date: Thu, 28 Mar 2013 18:00:06 +0000
To: www-dom@w3.org
Message-ID: <bug-21427-4009@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21427

            Bug ID: 21427
           Summary: Futures: use thenable
    Classification: Unclassified
           Product: WebAppsWG
           Version: unspecified
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: DOM
          Assignee: annevk@annevk.nl
          Reporter: annevk@annevk.nl
        QA Contact: public-webapps-bugzilla@w3.org
                CC: mike@w3.org, www-dom@w3.org

In http://dom.spec.whatwg.org/#concept-resolver-resolve add this for when the
branding check fails:

* Let /then/ be null.
* If /value/ is a JavaScript object, set /then/ to the result of invoking
/value/'s [[Get]] internal method for "then".
* If that throws an exception, invoke resolver's reject with the thrown
exception and terminate steps.
* If [[IsCallable]] /then/, run substeps: ... setup callbacks and invoke
/then/.

Now because this change resolver's resolvers can be invoked several times. So
http://dom.spec.whatwg.org/#concept-resolver needs to account for that by
checking and setting the resolved flag.

(Now we could see if there's some additional refactoring possible and we could
even do away with the branding check altogether, but changing that would
complicate the definition of then().)

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Thursday, 28 March 2013 18:00:08 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 28 March 2013 18:00:16 UTC