Bug 21444 - FutureResolver's resolve algorithm uses wrong resolver in new handlers
Summary: FutureResolver's resolve algorithm uses wrong resolver in new handlers
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: DOM (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Anne
QA Contact: public-webapps-bugzilla
URL: http://dom.spec.whatwg.org/#concept-r...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-03-30 15:48 UTC by Christophe Dumez
Modified: 2013-03-31 12:50 UTC (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christophe Dumez 2013-03-30 15:48:58 UTC
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.