Search results

Guidance on handling malicious/flawed [[Reject]] capability

Status: Open.

#113 In domenic/promises-unwrapping;

· getify opened on Jun 28, 2014

The spec should define which incumbent globals and entry globals are used, especially when enqueueing tasks.

abstract-underpinnings

question

Status: Open.

#108 In domenic/promises-unwrapping;

· nikhilm opened on May 20, 2014

What motivates the complicated dance for NewPromiseCapability?

question

Status: Open.

#104 In domenic/promises-unwrapping;

· domenic opened on Apr 7, 2014

Allow constructors to return new objects.

question

Status: Open.

#95 In domenic/promises-unwrapping;

· cscott opened on Feb 14, 2014

·  

Feature complete

Potential inconsistency in using [[PromiseConstructor]] in Promise Resolution Handler

normative-change

subclassing

Status: Open.

#94 In domenic/promises-unwrapping;

· domenic opened on Feb 13, 2014

·  

Feature complete

Spec creates strict requirements on subclass constructors

question

Status: Open.

#87 In domenic/promises-unwrapping;

· sicking opened on Dec 22, 2013

Add spec entry points that don't trigger user code

editorial

Status: Open.

#73 In domenic/promises-unwrapping;

· jorendorff opened on Nov 9, 2013

·  

Editorially complete

Convert tests to test-262 form

testable-implementation

Status: Open.

#69 In domenic/promises-unwrapping;

· domenic opened on Oct 30, 2013

·  

Tests complete

Add more tests for the API surface

es-manifestation

testable-implementation

Status: Open.

#68 In domenic/promises-unwrapping;

· domenic opened on Oct 30, 2013

·  

Tests complete