21427 2013-03-28 18:00:06 +0000 Futures: use thenable 2013-03-28 18:56:01 +0000 1 1 1 Unclassified WebAppsWG DOM unspecified PC All RESOLVED FIXED P2 normal --- 1 annevk annevk d mike www-dom public-webapps-bugzilla oldest_to_newest 85114 0 annevk 2013-03-28 18:00:06 +0000 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().) 85116 1 d 2013-03-28 18:31:46 +0000 > Now because this change resolver's resolvers can be invoked several times. This is already true, I think, because of future initialization. E.g. new Future(({ resolve, reject }) => { resolve(1); throw 2; }); 85118 2 annevk 2013-03-28 18:56:01 +0000 https://github.com/whatwg/dom/commit/77c556982412383cf27653bbbeb41c620aee62ee Thanks, sorry about raising stress levels. Just doing my best ;-)