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

[Bug 21444] New: FutureResolver's resolve algorithm uses wrong resolver in new handlers

From: <bugzilla@jessica.w3.org>
Date: Sat, 30 Mar 2013 15:48:58 +0000
To: www-dom@w3.org
Message-ID: <bug-21444-4009@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21444

            Bug ID: 21444
           Summary: FutureResolver's resolve algorithm uses wrong resolver
                    in new handlers
    Classification: Unclassified
           Product: WebAppsWG
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: DOM
          Assignee: annevk@annevk.nl
          Reporter: dchris@gmail.com
        QA Contact: public-webapps-bugzilla@w3.org
                CC: mike@w3.org, www-dom@w3.org

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.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Saturday, 30 March 2013 15:49:04 UTC

This archive was generated by hypermail 2.3.1 : Saturday, 30 March 2013 15:49:09 UTC