21444 2013-03-30 15:48:58 +0000 FutureResolver's resolve algorithm uses wrong resolver in new handlers 2013-03-31 12:50:42 +0000 1 1 1 Unclassified WebAppsWG DOM unspecified PC Linux RESOLVED FIXED http://dom.spec.whatwg.org/#concept-resolver-resolve P2 normal --- 1 chris annevk mike www-dom public-webapps-bugzilla oldest_to_newest 85173 0 chris 2013-03-30 15:48:58 +0000 The resolve algorithm currently states: """ If value is a future, run these substeps and then terminate these steps: Let accept be a new future handler whose type is resolve and resolver is value's associated resolver. Let reject be a new future handler whose type is reject and resolver is value's associated resolver. Append accept and reject to value. """ When implementing this in WebKit, I noticed that it did not work. I may be mistaken but I believe the new handlers' resolver should not be "value"'s associated resolver. Instead, it should be the *current* resolver. 85184 1 annevk 2013-03-31 12:50:42 +0000 https://github.com/whatwg/dom/commit/7f7d424ebc52d7667adac007bfcb5521af309c49