W3C home > Mailing lists > Public > www-dom@w3.org > April to June 2013

[Futures] Possible to multiply-resolve a resolver in weird ways

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Fri, 31 May 2013 00:46:56 -0400
Message-ID: <51A82B40.3030801@mit.edu>
To: DOM mailing list <www-dom@w3.org>
In the resolver's resolve algorithm, the first step is to check the 
"resolved flag" and bail out if set.  However the algorithm does not 
always set this flag.  Is that purposeful?

Even if I posit that it is, this leads to a slightly weird situation. 
Say I call resolve() with an object whose "then" getter accepts or 
rejects the resolver.  Then we'll end up calling the then method and 
passing in our new callbacks, even though the resolver is already resolved.

Should the resolved flag be rechecked after the [[Get]], perhaps?

Received on Friday, 31 May 2013 04:47:25 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:37:02 UTC