public-script-coord@w3.org from April to June 2013 by author

Alex Russell

• Re: Deprecating Future's .then() (Wednesday, 5 June)
• Re: Future feedback (Monday, 20 May)
• Re: Future feedback (Thursday, 9 May)
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? (Friday, 3 May)
• Re: Promise/Future: asynchrony in 'then' (Wednesday, 1 May)
• Re: Future cancellation (Wednesday, 1 May)
• Re: Future cancellation (Wednesday, 1 May)
• Re: Future cancellation (Tuesday, 30 April)
• Re: Futures (Saturday, 27 April)
• Re: Futures (Friday, 26 April)
• Re: A Challenge Problem for Promise Designers (was: Re: Futures) (Friday, 26 April)
• Re: Futures (Wednesday, 24 April)
• Re: Futures (Wednesday, 24 April)
• Re: Futures (was: Request for JSON-LD API review) (Friday, 19 April)
• Re: Futures (Wednesday, 17 April)
• Re: Coordination (was: ES6 Modules) (Friday, 12 April)
• Re: Coordination (was: ES6 Modules) (Friday, 12 April)

Allen Wirfs-Brock

• Re: Reconciling handling of optional arguments and handling of default values across ES and webidl (Tuesday, 18 June)
• Re: Reconciling handling of optional arguments and handling of default values across ES and webidl (Tuesday, 18 June)
• Re: Reconciling handling of optional arguments and handling of default values across ES and webidl (Tuesday, 18 June)
• A new ES6 spec. draft has been posted (Wednesday, 15 May)
• Re: Interface prototype objects and ES6 @@toStringTag (Monday, 13 May)
• Re: Interface prototype objects and ES6 @@toStringTag (Monday, 13 May)
• Re: Interface prototype objects and ES6 @@toStringTag (Monday, 13 May)
• Re: Reconciling handling of optional arguments and handling of default values across ES and webidl (Thursday, 9 May)
• Re: Web Alarm API - idiomatic check (Wednesday, 8 May)
• Re: Reconciling handling of optional arguments and handling of default values across ES and webidl (Wednesday, 8 May)
• Re: Web Alarm API - idiomatic check (Wednesday, 8 May)
• Re: Allowing IDL attributes to have different types for the getter and setter (Thursday, 18 April)
• Re: Coordination (Monday, 15 April)
• Re: Coordination (Monday, 15 April)
• Re: APIs that overload numbers and strings (Monday, 15 April)
• Re: APIs that overload numbers and strings (Monday, 15 April)
• Re: APIs that overload numbers and strings (Sunday, 14 April)
• Re: APIs that overload numbers and strings (Saturday, 13 April)
• Re: Coordination (Friday, 12 April)
• Re: Coordination (Friday, 12 April)
• Re: [webcomponents]: Platonic form of custom elements declarative syntax (Thursday, 11 April)
• Re: [webcomponents]: Platonic form of custom elements declarative syntax (Thursday, 11 April)
• Re: ES6 Modules (Monday, 8 April)
• Re: Catching exceptions (Tuesday, 2 April)

Andreas Rossberg

• Re: A Challenge Problem for Promise Designers (was: Re: Futures) (Tuesday, 21 May)
• Re: The Paradox of Partial Parametricity (Friday, 10 May)
• Re: The Paradox of Partial Parametricity (Friday, 10 May)
• Re: Reconciling handling of optional arguments and handling of default values across ES and webidl (Thursday, 9 May)
• Re: Reconciling handling of optional arguments and handling of default values across ES and webidl (Thursday, 9 May)
• Re: What Are We Arguing About? (was: Re: A Challenge Problem for Promise Designers) (Monday, 29 April)
• Re: A Challenge Problem for Promise Designers (Friday, 26 April)
• Re: A Challenge Problem for Promise Designers (Friday, 26 April)
• Re: A Challenge Problem for Promise Designers (was: Re: Futures) (Friday, 26 April)

Anne van Kesteren

• Re: undefined values in dictionaries (Monday, 24 June)
• Re: [promises] Difficulties with using constructors and promises together (Thursday, 20 June)
• Re: Request for API design feedback: Web MIDI API (Monday, 10 June)
• Re: Deprecating Future's .then() (Wednesday, 5 June)
• Re: Deprecating Future's .then() (Wednesday, 5 June)
• Re: Deprecating Future's .then() (Wednesday, 5 June)
• Re: Deprecating Future's .then() (Tuesday, 4 June)
• Re: Deprecating Future's .then() (Monday, 3 June)
• Re: Deprecating Future's .then() (Monday, 3 June)
• Re: URL/URI APIs (Tuesday, 21 May)
• Re: Future cancellation (Thursday, 2 May)
• Re: Future cancellation (Thursday, 2 May)
• Re: Future cancellation (Wednesday, 1 May)
• Re: Futures (Friday, 26 April)
• Re: Futures (Friday, 26 April)
• Re: Futures (was: Request for JSON-LD API review) (Wednesday, 24 April)
• Re: ES6,ES7,ES8 and beyond. A Proposed Roadmap. (Wednesday, 24 April)
• Re: Futures (Monday, 22 April)
• Re: Futures (Monday, 22 April)
• Re: Futures (was: Request for JSON-LD API review) (Thursday, 18 April)
• Re: Futures (was: Request for JSON-LD API review) (Wednesday, 17 April)
• Re: Futures (was: Request for JSON-LD API review) (Wednesday, 17 April)
• Re: Futures (was: Request for JSON-LD API review) (Wednesday, 17 April)
• Re: APIs that overload numbers and strings (Monday, 15 April)
• Re: Coordination (was: ES6 Modules) (Saturday, 13 April)
• Re: Coordination (Saturday, 13 April)
• Re: Coordination (Saturday, 13 April)
• Re: Coordination (Friday, 12 April)
• Re: Coordination (was: ES6 Modules) (Friday, 12 April)
• Re: Structured clones (Thursday, 11 April)
• Structured clones (Wednesday, 10 April)
• Re: ES6 Modules (Tuesday, 9 April)
• Re: ES6 Modules (Tuesday, 9 April)
• Re: ES6 Modules (Monday, 8 April)
• Re: ES6 Modules (Monday, 8 April)
• ES6 Modules (Monday, 8 April)
• Re: Catching exceptions (Tuesday, 2 April)
• Catching exceptions (Tuesday, 2 April)

Arthur Barstow

• RfC: 2nd Last Call of "Vibration API"; deadline June 13 (Tuesday, 28 May)
• Fwd: CfC: publish Java bindings for WebIDL as a WG Note; deadline May 4 (Monday, 29 April)
• Re: Coordination (Monday, 15 April)
• Re: Coordination (Sunday, 14 April)

Aymeric Vitte

• Re: Coordination (Monday, 15 April)

Bill Frantz

• Re: Future cancellation (Thursday, 2 May)
• Re: Future cancellation (Thursday, 2 May)
• Re: Future cancellation (Wednesday, 1 May)
• Re: Future cancellation (Wednesday, 1 May)
• Re: Future cancellation (Wednesday, 1 May)
• Promises in E (was Re: A Challenge Problem for Promise Designers) (Friday, 26 April)
• Re: Promises in E (was Re: A Challenge Problem for Promise Designers) (Friday, 26 April)

Bjoern Hoehrmann

• Re: URL/URI APIs (Tuesday, 21 May)
• Re: Future cancellation (Wednesday, 1 May)
• Re: Future cancellation (Wednesday, 1 May)

Boris Zbarsky

• Re: WebIDL generated TypeErrors and promises (Saturday, 29 June)
• Re: WebIDL generated TypeErrors and promises (Friday, 28 June)
• Re: WebIDL generated TypeErrors and promises (Friday, 28 June)
• Re: WebIDL generated TypeErrors and promises (Friday, 28 June)
• Re: [webidl] Add a [Maplike] tag? (Thursday, 27 June)
• Re: [webidl] Add a [Maplike] tag? (Thursday, 27 June)
• Re: [webidl] Add a [Maplike] tag? (Thursday, 27 June)
• Re: Guidance on using sequences and arrays (Wednesday, 26 June)
• Re: Guidance on using sequences and arrays (Wednesday, 26 June)
• Re: Guidance on using sequences and arrays (Wednesday, 26 June)
• Re: Guidance on using sequences and arrays (Wednesday, 26 June)
• Re: undefined values in dictionaries (Monday, 24 June)
• Re: undefined values in dictionaries (Monday, 24 June)
• Re: Reconciling handling of optional arguments and handling of default values across ES and webidl (Tuesday, 18 June)
• Re: Reconciling handling of optional arguments and handling of default values across ES and webidl (Tuesday, 18 June)
• Re: undefined values in dictionaries (Tuesday, 18 June)
• Re: Reconciling handling of optional arguments and handling of default values across ES and webidl (Tuesday, 18 June)
• Re: Question about implements statements (Monday, 17 June)
• Re: Question about implements statements (Monday, 17 June)
• Re: undefined values in dictionaries (Wednesday, 12 June)
• Re: undefined values in dictionaries (Wednesday, 12 June)
• Re: undefined values in dictionaries (Wednesday, 12 June)
• Re: undefined values in dictionaries (Wednesday, 12 June)
• Re: undefined values in dictionaries (Wednesday, 12 June)
• undefined values in dictionaries (Tuesday, 11 June)
• Re: [Futures] accept/resolve/reject on a resolver don't have clearly defined behavior if no value is passed (Friday, 7 June)
• Re: resolving references when object from other security context is in scope (Friday, 7 June)
• Re: [Futures] accept/resolve/reject on a resolver don't have clearly defined behavior if no value is passed (Thursday, 6 June)
• [webidl] Section on serializer ES bindings has copy/paste "stringifier" (Saturday, 1 June)
• Re: Fwd: [webidl] Add a [Maplike] tag? (Thursday, 30 May)
• Re: FileList (and other Array-like types) (Thursday, 30 May)
• Re: FileList (and other Array-like types) (Thursday, 30 May)
• Re: FileList (and other Array-like types) (Thursday, 30 May)
• Re: Future feedback (Friday, 17 May)
• Re: Future feedback (Thursday, 16 May)
• Re: Future feedback (Thursday, 16 May)
• Re: Future feedback (Thursday, 16 May)
• Re: Future feedback (Wednesday, 15 May)
• Re: Future feedback (Tuesday, 14 May)
• Re: Future feedback (Tuesday, 14 May)
• Re: Future feedback (Tuesday, 14 May)
• Re: Future feedback (Tuesday, 14 May)
• Re: Interface prototype objects and ES6 @@toStringTag (Monday, 13 May)
• Re: Future feedback (Monday, 13 May)
• Re: Reconciling handling of optional arguments and handling of default values across ES and webidl (Friday, 10 May)
• Re: Reconciling handling of optional arguments and handling of default values across ES and webidl (Friday, 10 May)
• Re: Reconciling handling of optional arguments and handling of default values across ES and webidl (Thursday, 9 May)
• Re: Reconciling handling of optional arguments and handling of default values across ES and webidl (Thursday, 9 May)
• Re: Reconciling handling of optional arguments and handling of default values across ES and webidl (Thursday, 9 May)
• Re: Reconciling handling of optional arguments and handling of default values across ES and webidl (Thursday, 9 May)
• Re: Reconciling handling of optional arguments and handling of default values across ES and webidl (Thursday, 9 May)
• Re: Reconciling handling of optional arguments and handling of default values across ES and webidl (Thursday, 9 May)
• Re: Reconciling handling of optional arguments and handling of default values across ES and webidl (Thursday, 9 May)
• Re: Reconciling handling of optional arguments and handling of default values across ES and webidl (Wednesday, 8 May)
• Reconciling handling of optional arguments and handling of default values across ES and webidl (Wednesday, 8 May)
• Re: [Future] First arguments should not be optional (Wednesday, 8 May)
• Re: Future feedback (Wednesday, 8 May)
• Why is [Constructor] not allowed on partial interfaces? (Monday, 6 May)
• Re: Allowing IDL attributes to have different types for the getter and setter (Thursday, 18 April)
• Re: Allowing IDL attributes to have different types for the getter and setter (Thursday, 18 April)
• Re: Allowing IDL attributes to have different types for the getter and setter (Thursday, 18 April)
• Allowing IDL attributes to have different types for the getter and setter (Thursday, 18 April)
• Re: Futures (Wednesday, 17 April)
• Re: APIs that overload numbers and strings (Monday, 15 April)
• Re: APIs that overload numbers and strings (Monday, 15 April)
• Re: APIs that overload numbers and strings (Monday, 15 April)
• Re: Coordination (Sunday, 14 April)
• Re: APIs that overload numbers and strings (Sunday, 14 April)
• APIs that overload numbers and strings (Saturday, 13 April)
• Re: Coordination (Saturday, 13 April)
• Re: Coordination (Saturday, 13 April)
• Re: Coordination (Friday, 12 April)
• Re: Coordination (Friday, 12 April)
• Re: Coordination (Friday, 12 April)
• Re: [webcomponents]: Platonic form of custom elements declarative syntax (Thursday, 11 April)
• Re: [webcomponents]: Platonic form of custom elements declarative syntax (Thursday, 11 April)
• Re: [webcomponents]: Platonic form of custom elements declarative syntax (Thursday, 11 April)

Brandon Benvie

• Re: Reconciling handling of optional arguments and handling of default values across ES and webidl (Wednesday, 8 May)
• Re: Reconciling handling of optional arguments and handling of default values across ES and webidl (Wednesday, 8 May)

Brendan Eich

• Re: undefined values in dictionaries (Wednesday, 12 June)
• Re: [Futures] accept/resolve/reject on a resolver don't have clearly defined behavior if no value is passed (Friday, 7 June)
• Re: Future cancellation (Tuesday, 30 April)
• Re: Futures (Saturday, 20 April)
• Re: Futures (Saturday, 20 April)
• Re: Futures (Saturday, 20 April)
• Re: Coordination (Sunday, 14 April)
• Re: Coordination (Saturday, 13 April)
• Re: Coordination (Saturday, 13 April)
• Re: Coordination (Saturday, 13 April)
• Re: Coordination (Friday, 12 April)
• Re: ES6 Modules (Tuesday, 9 April)
• Re: ES6 Modules (Tuesday, 9 April)

Brian Kardell

• Re: Coordination (was: ES6 Modules) (Friday, 12 April)

bugzilla@jessica.w3.org

• [Bug 22522] New: WebIDL, error handling, and promises (Sunday, 30 June)
• [Bug 22509] Some way to express array as readonly and fixed length (Saturday, 29 June)
• [Bug 22509] Some way to express array as readonly and fixed length (Saturday, 29 June)
• [Bug 22509] Some way to express array as readonly and fixed length (Friday, 28 June)
• [Bug 22509] Some way to express array as readonly and fixed length (Friday, 28 June)
• [Bug 22509] New: Some way to express array as readonly and fixed length (Friday, 28 June)
• [Bug 22507] New: Need to define behaviour for setting properties on named properties objects (Friday, 28 June)
• [Bug 22506] New: Named properties object should probably not be a function object (Friday, 28 June)
• [Bug 21422] Generic Promise type notation (Thursday, 27 June)
• [Bug 21422] Generic Promise type notation (Thursday, 27 June)
• [Bug 21422] Generic Promise type notation (Thursday, 27 June)
• [Bug 21422] Generic Promise type notation (Thursday, 27 June)
• [Bug 22392] maybe define .name for Function objects corresponding to operations/attributes (Tuesday, 18 June)
• [Bug 22392] maybe define .name for Function objects corresponding to operations/attributes (Tuesday, 18 June)
• [Bug 22320] Form's supported property names should perhaps not be enumerable (Tuesday, 18 June)
• [Bug 22392] maybe define .name for Function objects corresponding to operations/attributes (Tuesday, 18 June)
• [Bug 22392] maybe define .name for Function objects corresponding to operations/attributes (Tuesday, 18 June)
• [Bug 22320] Form's supported property names should perhaps not be enumerable (Monday, 17 June)
• [Bug 22392] New: maybe define .name for Function objects corresponding to operations/attributes (Monday, 17 June)
• [Bug 22391] New: Sequence or Array (Monday, 17 June)
• [Bug 22358] Add a "this is the global" annotation (Monday, 17 June)
• [Bug 22346] Security: When invoking a method, getter, or setter on an object using the property descriptor of another, we need to do a security check (Monday, 17 June)
• [Bug 22312] Typo? (Monday, 17 June)
• [Bug 22168] An attribute cannot be a dictionary type (Monday, 17 June)
• [Bug 22156] Allow trailing commas in Web IDL lists (Monday, 17 June)
• [Bug 21929] named properties object should disallow definition of non-configurable properties (Monday, 17 June)
• [Bug 21670] Clarify that typeof InterfaceObject should be "function" (Monday, 17 June)
• [Bug 21669] Callable interface objects should be instance of Function (Monday, 17 June)
• [Bug 21640] Dictionaries and callbacks should be distinguishable (Monday, 17 June)
• [Bug 21591] String constant on NavigatorID is invalid per WebIDL (Monday, 17 June)
• [Bug 21589] SelectionMode enum should not have a trailing comma (Monday, 17 June)
• [Bug 21295] overload resolution: are DOMString and sequence<T> distinguishable now? (Monday, 17 June)
• [Bug 20777] Getting a property from the global scope polluter ends up in an infinite loop (Monday, 17 June)
• [Bug 20653] Function object doesn't specify needing a "prototype" property (Monday, 17 June)
• [Bug 20561] Objects supporting indexed properties (Monday, 17 June)
• [Bug 20535] consider removing indexed property setters, creators and deleters (Monday, 17 June)
• [Bug 20528] Definition of [[Prototype]] for the interface prototype object is confusing (Monday, 17 June)
• [Bug 20527] Comment about NamedPropertiesObject is incorrect (Monday, 17 June)
• [Bug 20481] Grammar Fixes needed: Dominique's feedback + Microsoft's feedback (Monday, 17 June)
• [Bug 20478] Grammar allows "static;" as a valid operation (Monday, 17 June)
• [Bug 20475] Grammar allows "- Infinity", but not "- 1" (Monday, 17 June)
• [Bug 20458] 4.2.22: converting IDL value to IDL type? (Monday, 17 June)
• [Bug 20456] 4.2.24.1: wrong conversion (Monday, 17 June)
• [Bug 20455] converting to an ECMAScript value [of a specified type??] (Monday, 17 June)
• [Bug 20453] 3.1: two questions re underscore removal (Monday, 17 June)
• [Bug 20452] 4.2.16: extraneous "the" (Monday, 17 June)
• [Bug 20444] 4.*: "descriptor { ... }" (Monday, 17 June)
• [Bug 20443] 4.4.6: "is not of the enumeration’s values" (Monday, 17 June)
• [Bug 20442] 4.2.24: <ul> should be <ol> (Monday, 17 June)
• [Bug 20440] 4.4.1.1: "of it type list" (Monday, 17 June)
• [Bug 20439] 4.4.6: <span class="desc"> (Monday, 17 June)
• [Bug 20422] 4.2.21: "then then" (Monday, 17 June)
• [Bug 20419] 4.2.24.2: missing "then"? (Monday, 17 June)
• [Bug 20225] don't allow overridden operations and attribute getters/setters to be invoked on descendant objects (Monday, 17 June)
• [Bug 20008] allow [Unforgeable] on an interface (Monday, 17 June)
• [Bug 19988] add a [LenientFloat] to mean "ignore IDL attribute assignment or method call if a non-finite float is passed" (Monday, 17 June)
• [Bug 19936] consider allowing non-matching enums to be converted to a particular value (Monday, 17 June)
• [Bug 18908] Consider disallowing expandos on objects with a named getter but no named setter (Monday, 17 June)
• [Bug 18547] Add [ImplicitThis] to EventTarget? (Monday, 17 June)
• [Bug 18362] Make stringifiers not take into account expandos (Monday, 17 June)
• [Bug 18352] Note about Object.prototype.toString is unclear (Monday, 17 June)
• [Bug 17713] Exceptions thrown from event handlers should not be propagated (Monday, 17 June)
• [Bug 16833] consider always exposing a "length" property for objects with indexed properties (Monday, 17 June)
• [Bug 16767] Allow user objects for Array[] types (Monday, 17 June)
• [Bug 16604] RFE: add unsigned byte as synonym for octet (Monday, 17 June)
• [Bug 16537] Interface types - Implements is ambiguous (Monday, 17 June)
• [Bug 16455] Using platform object example (Monday, 17 June)
• [Bug 22358] Add a "this is the global" annotation (Friday, 14 June)
• [Bug 22358] Add a "this is the global" annotation (Friday, 14 June)
• [Bug 22358] New: Add a "this is the global" annotation (Friday, 14 June)
• [Bug 22346] Security: When invoking a method, getter, or setter on an object using the property descriptor of another, we need to do a security check (Thursday, 13 June)
• [Bug 22346] New: Security: When invoking a method, getter, or setter on an object using the property descriptor of another, we need to do a security check (Thursday, 13 June)
• [Bug 22312] New: Typo? (Saturday, 8 June)
• [Bug 22168] An attribute cannot be a dictionary type (Tuesday, 28 May)
• [Bug 22168] An attribute cannot be a dictionary type (Tuesday, 28 May)
• [Bug 21591] String constant on NavigatorID is invalid per WebIDL (Monday, 27 May)
• [Bug 22168] An attribute cannot be a dictionary type (Sunday, 26 May)
• [Bug 22168] New: An attribute cannot be a dictionary type (Sunday, 26 May)
• [Bug 21589] SelectionMode enum should not have a trailing comma (Friday, 24 May)
• [Bug 21589] SelectionMode enum should not have a trailing comma (Friday, 24 May)
• [Bug 21589] SelectionMode enum should not have a trailing comma (Friday, 24 May)
• [Bug 17508] Let enum lists end with a comma (Friday, 24 May)
• [Bug 22156] Allow trailing commas in Web IDL lists (Friday, 24 May)
• [Bug 21589] SelectionMode enum should not have a trailing comma (Friday, 24 May)
• [Bug 22156] New: Allow trailing commas in Web IDL lists (Friday, 24 May)
• [Bug 19778] Wrong regex for integer (Friday, 24 May)
• [Bug 19778] Wrong regex for integer (Friday, 24 May)
• [Bug 22014] newly created exception objects should have the exception prototype interface object as their [[Prototype]] (Sunday, 12 May)
• [Bug 22014] New: newly created exception objects should have the exception prototype interface object as their [[Prototype]] (Sunday, 12 May)
• [Bug 22013] property enumeration section should mention named property visibility (Sunday, 12 May)
• [Bug 22013] New: property enumeration section should mention named property visibility (Sunday, 12 May)
• [Bug 22006] need to define that the .length of a stringifier's Function object is 0 (Saturday, 11 May)
• [Bug 22006] New: need to define that the .length of a stringifier's Function object is 0 (Saturday, 11 May)
• [Bug 21422] Futures (Wednesday, 8 May)
• [Bug 21929] New: named properties object should disallow definition of non-configurable properties (Sunday, 5 May)
• [Bug 20019] Support subclassing ES6 Map (Tuesday, 23 April)
• [Bug 21591] String constant on NavigatorID is invalid per WebIDL (Monday, 15 April)
• [Bug 21670] Clarify that typeof InterfaceObject should be "function" (Friday, 12 April)
• [Bug 21640] Dictionaries and callbacks should be distinguishable (Friday, 12 April)
• [Bug 21640] Dictionaries and callbacks should be distinguishable (Friday, 12 April)
• [Bug 21640] Dictionaries and callbacks should be distinguishable (Friday, 12 April)
• [Bug 21640] Dictionaries and callbacks should be distinguishable (Friday, 12 April)
• [Bug 21640] Dictionaries and callbacks should be distinguishable (Friday, 12 April)
• [Bug 21640] Dictionaries and callbacks should be distinguishable (Friday, 12 April)
• [Bug 21640] Dictionaries and callbacks should be distinguishable (Friday, 12 April)
• [Bug 21640] Dictionaries and callbacks should be distinguishable (Friday, 12 April)
• [Bug 21640] Dictionaries and callbacks should be distinguishable (Friday, 12 April)
• [Bug 21640] Dictionaries and callbacks should be distinguishable (Friday, 12 April)
• [Bug 21640] Dictionaries and callbacks should be distinguishable (Friday, 12 April)
• [Bug 21640] Dictionaries and callbacks should be distinguishable (Friday, 12 April)
• [Bug 21640] Dictionaries and callbacks should be distinguishable (Friday, 12 April)
• [Bug 21591] String constant on NavigatorID is invalid per WebIDL (Friday, 12 April)
• [Bug 21591] String constant on NavigatorID is invalid per WebIDL (Friday, 12 April)
• [Bug 21591] String constant on NavigatorID is invalid per WebIDL (Friday, 12 April)
• [Bug 21591] String constant on NavigatorID is invalid per WebIDL (Friday, 12 April)
• [Bug 21591] String constant on NavigatorID is invalid per WebIDL (Thursday, 11 April)
• [Bug 21670] Clarify that typeof InterfaceObject should be "function" (Thursday, 11 April)
• [Bug 21670] Clarify that typeof InterfaceObject should be "function" (Thursday, 11 April)
• [Bug 21669] Callable interface objects should be instance of Function (Thursday, 11 April)
• [Bug 21589] SelectionMode enum should not have a trailing comma (Thursday, 11 April)
• [Bug 21591] String constant on NavigatorID is invalid per WebIDL (Thursday, 11 April)
• [Bug 21670] New: Clarify that typeof InterfaceObject should be "function" (Thursday, 11 April)
• [Bug 21669] New: Callable interface objects should be instance of Function (Thursday, 11 April)
• [Bug 21640] New: Dictionaries and callbacks should be distinguishable (Tuesday, 9 April)
• [Bug 21492] Typo about preventExtensions (Monday, 1 April)
• [Bug 21492] New: Typo about preventExtensions (Monday, 1 April)

Cameron McCormack

• Re: [webidl] Add a [Maplike] tag? (Thursday, 27 June)
• Re: Reconciling handling of optional arguments and handling of default values across ES and webidl (Monday, 24 June)
• Re: undefined values in dictionaries (Sunday, 23 June)
• Re: undefined values in dictionaries (Tuesday, 18 June)
• Re: Reconciling handling of optional arguments and handling of default values across ES and webidl (Tuesday, 18 June)
• Re: Extended attributes on WebIDL typedefs need to be defined better, or just dropped (Tuesday, 18 June)
• Re: Off-by-one error in double to long long conversion ? (Tuesday, 18 June)
• Re: Question about implements statements (Monday, 17 June)
• Re: WebIDL should define "native Array" (Monday, 17 June)
• Re: Question about implements statements (Monday, 17 June)
• Re: undefined values in dictionaries (Thursday, 13 June)
• Re: [Futures] accept/resolve/reject on a resolver don't have clearly defined behavior if no value is passed (Saturday, 8 June)
• Re: [webidl] Section on serializer ES bindings has copy/paste "stringifier" (Saturday, 1 June)
• test suite for Web IDL v1 (Monday, 13 May)

Charles McCathie Nevile

• URL/URI APIs (Sunday, 19 May)
• Webapps face to face meeting summary (Friday, 10 May)
• Re: Coordination (Monday, 15 April)
• Re: Coordination (Friday, 12 April)

Christophe Dumez - SISA

• RE: Web Alarm API - idiomatic check (Thursday, 9 May)

David Bruant

• Re: Specs and Object.observe() (Monday, 17 June)
• Re: Future feedback (Wednesday, 15 May)
• Re: Future feedback (Tuesday, 14 May)
• Re: Future feedback (Tuesday, 14 May)
• Re: Future feedback (Tuesday, 14 May)
• Re: Future feedback (Friday, 10 May)
• Re: A Challenge Problem for Promise Designers (Friday, 26 April)
• Re: A Challenge Problem for Promise Designers (Friday, 26 April)
• Re: What Are We Arguing About? (was: Re: A Challenge Problem for Promise Designers) (Friday, 26 April)
• Re: What Are We Arguing About? (was: Re: A Challenge Problem for Promise Designers) (Friday, 26 April)
• Re: A Challenge Problem for Promise Designers (Friday, 26 April)
• Re: A Challenge Problem for Promise Designers (Friday, 26 April)
• Re: A Challenge Problem for Promise Designers (Friday, 26 April)
• Re: A Challenge Problem for Promise Designers (was: Re: Futures) (Friday, 26 April)
• Re: please review and comment for my draft (Thursday, 25 April)
• Re: ES6,ES7,ES8 and beyond. A Proposed Roadmap. (Wednesday, 24 April)
• Re: Futures (Wednesday, 24 April)
• Re: Futures (Tuesday, 23 April)
• Re: Futures (Tuesday, 23 April)
• Re: Futures (Tuesday, 23 April)
• Re: Futures (Monday, 22 April)
• Re: Futures (Monday, 22 April)
• Re: Futures (Monday, 22 April)
• Re: Futures (Monday, 22 April)
• Re: Futures (Monday, 22 April)
• Re: More flexibility in the ECMAScript part? (Thursday, 18 April)
• Re: Allowing IDL attributes to have different types for the getter and setter (Thursday, 18 April)
• Re: Coordination (Sunday, 14 April)
• Re: Coordination (Saturday, 13 April)
• Re: ES6 Modules (Monday, 8 April)

David Sheets

• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? (Wednesday, 8 May)
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? (Wednesday, 8 May)
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? (Tuesday, 7 May)
• Re: A Challenge Problem for Promise Designers (Sunday, 28 April)
• Re: A Challenge Problem for Promise Designers (Sunday, 28 April)
• Fwd: A Challenge Problem for Promise Designers (Saturday, 27 April)
• Re: A Challenge Problem for Promise Designers (Saturday, 27 April)
• Re: Futures (Friday, 26 April)
• Re: A Challenge Problem for Promise Designers (was: Re: Futures) (Friday, 26 April)
• Re: A Challenge Problem for Promise Designers (was: Re: Futures) (Friday, 26 April)
• Re: A Challenge Problem for Promise Designers (was: Re: Futures) (Friday, 26 April)
• Re: A Challenge Problem for Promise Designers (was: Re: Futures) (Friday, 26 April)
• Re: Futures (Tuesday, 23 April)

Dean Landolt

• Re: A Challenge Problem for Promise Designers (Saturday, 27 April)
• Re: A Challenge Problem for Promise Designers (Friday, 26 April)
• Re: A Challenge Problem for Promise Designers (Friday, 26 April)
• Re: ES6,ES7,ES8 and beyond. A Proposed Roadmap. (Wednesday, 24 April)
• Re: Futures (Tuesday, 23 April)
• Re: Futures (Tuesday, 23 April)
• Re: Futures (Tuesday, 23 April)
• Re: Futures (Monday, 22 April)
• Re: Futures (Monday, 22 April)
• Re: Futures (Monday, 22 April)
• Re: Futures (Monday, 22 April)
• Re: Futures (Monday, 22 April)

Dirk Pranke

• Re: Coordination (was: ES6 Modules) (Sunday, 14 April)
• Re: Coordination (was: ES6 Modules) (Saturday, 13 April)
• Re: Coordination (was: ES6 Modules) (Saturday, 13 April)
• Re: Outreach? (was Coordination/ES6 Modules) (Saturday, 13 April)
• Outreach? (was Coordination/ES6 Modules) (Saturday, 13 April)
• Re: Coordination (was: ES6 Modules) (Saturday, 13 April)

Domenic Denicola

• RE: WebIDL generated TypeErrors and promises (Friday, 28 June)
• Re: WebIDL generated TypeErrors and promises (Friday, 28 June)
• RE: Guidance on using sequences and arrays (Wednesday, 26 June)
• RE: Specs and Object.observe() (Monday, 17 June)
• RE: Deprecating Future's .then() (Tuesday, 4 June)
• RE: Future feedback (Thursday, 16 May)
• RE: Reconciling handling of optional arguments and handling of default values across ES and webidl (Wednesday, 8 May)
• RE: Web Alarm API - idiomatic check (Wednesday, 8 May)
• RE: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? (Friday, 3 May)
• RE: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? (Thursday, 2 May)
• RE: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? (Thursday, 2 May)
• RE: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? (Thursday, 2 May)
• RE: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? (Thursday, 2 May)
• RE: Future cancellation (Wednesday, 1 May)
• RE: Promise/Future: asynchrony in 'then' (Wednesday, 1 May)
• RE: Future cancellation (Wednesday, 1 May)
• RE: Future cancellation (Wednesday, 1 May)
• RE: A Challenge Problem for Promise Designers (Friday, 26 April)
• RE: A Challenge Problem for Promise Designers (Friday, 26 April)
• RE: Futures (Friday, 26 April)
• RE: Futures (Friday, 26 April)
• RE: What Are We Arguing About? (was: Re: A Challenge Problem for Promise Designers) (Friday, 26 April)
• RE: A Challenge Problem for Promise Designers (was: Re: Futures) (Friday, 26 April)
• RE: A Challenge Problem for Promise Designers (was: Re: Futures) (Friday, 26 April)
• RE: A Challenge Problem for Promise Designers (was: Re: Futures) (Friday, 26 April)
• RE: Futures (Monday, 22 April)
• RE: Allowing IDL attributes to have different types for the getter and setter (Thursday, 18 April)
• RE: Allowing IDL attributes to have different types for the getter and setter (Thursday, 18 April)

Ehsan Akhgari

• Re: APIs that overload numbers and strings (Monday, 15 April)
• Re: APIs that overload numbers and strings (Monday, 15 April)
• Re: APIs that overload numbers and strings (Monday, 15 April)

Erik Arvidsson

• Re: Interface prototype objects and ES6 @@toStringTag (Monday, 13 May)
• Re: Interface prototype objects and ES6 @@toStringTag (Monday, 13 May)
• Interface prototype objects and ES6 @@toStringTag (Monday, 13 May)
• Class side inheritance in WebIDL (was Re: [webcomponents]: Platonic form of custom elements declarative syntax) (Thursday, 11 April)
• Re: ES6 Modules (Monday, 8 April)

François REMY

• Re: [promises] Difficulties with using constructors and promises together (Thursday, 20 June)
• Re: Specs and Object.observe() (Monday, 17 June)

Garrett Smith

• Re: URL/URI APIs (Monday, 20 May)
• Re: Reconciling handling of optional arguments and handling of default values across ES and webidl (Thursday, 9 May)
• Re: Reconciling handling of optional arguments and handling of default values across ES and webidl (Thursday, 9 May)
• Re: Reconciling handling of optional arguments and handling of default values across ES and webidl (Wednesday, 8 May)
• Re: [Future] First arguments should not be optional (Wednesday, 8 May)

Hallvord Reiar M. Steen

• resolving references when object from other security context is in scope (Friday, 7 June)

Hallvord Reiar Michaelsen Steen

• Re: resolving references when object from other security context is in scope (Friday, 7 June)

Jake Verbaten

• Re: Web Alarm API - idiomatic check (Wednesday, 8 May)
• Re: Web Alarm API - idiomatic check (Wednesday, 8 May)
• Re: Web Alarm API - idiomatic check (Wednesday, 8 May)
• Re: Web Alarm API - idiomatic check (Wednesday, 8 May)

Jonas Sicking

• Re: undefined values in dictionaries (Wednesday, 12 June)
• Re: [Futures] accept/resolve/reject on a resolver don't have clearly defined behavior if no value is passed (Friday, 7 June)
• Re: FileList (and other Array-like types) (Thursday, 30 May)
• FileList (and other Array-like types) (Thursday, 30 May)
• Re: Review Request: Raw Socket API (Monday, 20 May)
• Re: Web Alarm API - idiomatic check (Wednesday, 15 May)
• Re: Future feedback (Tuesday, 14 May)
• Re: Future feedback (Monday, 13 May)
• Re: Reconciling handling of optional arguments and handling of default values across ES and webidl (Friday, 10 May)
• Re: [Alarm API] Time zone handling (Friday, 10 May)
• Re: [Alarm API] Time zone handling (Friday, 10 May)
• Re: [Alarm API] Time zone handling (Friday, 10 May)
• Re: [Alarm API] Time zone handling (Friday, 10 May)
• Re: [Alarm API] Time zone handling (Friday, 10 May)
• Re: [Alarm API] Time zone handling (Thursday, 9 May)
• Re: Web Alarm API - idiomatic check (Wednesday, 8 May)
• Re: Web Alarm API - idiomatic check (Wednesday, 8 May)
• Re: Reconciling handling of optional arguments and handling of default values across ES and webidl (Wednesday, 8 May)
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? (Wednesday, 8 May)
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? (Tuesday, 7 May)
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? (Tuesday, 7 May)
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? (Monday, 6 May)
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? (Monday, 6 May)
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? (Friday, 3 May)
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? (Thursday, 2 May)
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? (Thursday, 2 May)
• Re: Future cancellation (Wednesday, 1 May)
• Re: Future cancellation (Wednesday, 1 May)
• Re: Future cancellation (Wednesday, 1 May)
• Re: Future cancellation (Wednesday, 1 May)
• Re: Future cancellation (Wednesday, 1 May)
• Re: Future cancellation (Tuesday, 30 April)
• Re: Futures (Saturday, 20 April)
• Re: APIs that overload numbers and strings (Sunday, 14 April)

Jorge

• Re: Future feedback (Tuesday, 14 May)
• Re: Future feedback (Tuesday, 14 May)
• Re: Future feedback (Tuesday, 14 May)
• Re: Web Alarm API - idiomatic check (Wednesday, 8 May)
• Re: Web Alarm API - idiomatic check (Wednesday, 8 May)
• Re: Futures (was: Request for JSON-LD API review) (Thursday, 18 April)
• Re: More flexibility in the ECMAScript part? (Thursday, 18 April)

Joshua Bell

• Re: Web Alarm API - idiomatic check (Wednesday, 8 May)

Juan Ignacio Dopazo

• Re: Future cancellation (Wednesday, 1 May)
• Re: Future cancellation (Tuesday, 30 April)
• Re: Futures (Friday, 26 April)
• Re: What Are We Arguing About? (was: Re: A Challenge Problem for Promise Designers) (Friday, 26 April)
• Re: Futures (Friday, 26 April)
• Re: Futures (Friday, 26 April)
• Re: A Challenge Problem for Promise Designers (was: Re: Futures) (Friday, 26 April)
• Re: Futures (Wednesday, 24 April)

Jussi Kalliokoski

• Request for API design feedback: Web MIDI API (Saturday, 8 June)

Kevin Gadd

• Re: Future cancellation (Wednesday, 1 May)
• Re: Future cancellation (Wednesday, 1 May)
• Do futures represent a pipeline? (was Re: Future cancellation) (Tuesday, 30 April)
• Re: Future cancellation (Tuesday, 30 April)
• Re: Future cancellation (Tuesday, 30 April)

Kevin Reid

• Re: Interface prototype objects and ES6 @@toStringTag (Monday, 13 May)

Kevin Smith

• Re: The Paradox of Partial Parametricity (Friday, 10 May)
• Re: Future cancellation (Wednesday, 1 May)
• Re: Future cancellation (Wednesday, 1 May)
• Re: Future cancellation (Tuesday, 30 April)
• Re: Futures (Friday, 26 April)
• Re: Futures (Friday, 26 April)
• Re: Futures (Friday, 26 April)
• Re: Futures (Friday, 26 April)
• Re: Futures (Friday, 26 April)
• Re: Futures (Friday, 26 April)
• Re: A Challenge Problem for Promise Designers (was: Re: Futures) (Friday, 26 April)
• Re: A Challenge Problem for Promise Designers (was: Re: Futures) (Friday, 26 April)
• Re: A Challenge Problem for Promise Designers (was: Re: Futures) (Friday, 26 April)
• Re: Futures (Monday, 22 April)
• Re: Futures (Monday, 22 April)
• Re: Futures (Monday, 22 April)
• Re: Futures (Monday, 22 April)
• Re: Futures (Sunday, 21 April)
• Re: More flexibility in the ECMAScript part? (Thursday, 18 April)
• Re: Futures (was: Request for JSON-LD API review) (Wednesday, 17 April)
• Re: Coordination (was: ES6 Modules) (Sunday, 14 April)
• Re: Coordination (was: ES6 Modules) (Saturday, 13 April)
• Re: ES6 Modules (Monday, 8 April)

Kris Kowal

• Re: Do futures represent a pipeline? (was Re: Future cancellation) (Wednesday, 1 May)

Lucas Smith

• Re: Future cancellation (Tuesday, 30 April)

Manu Sporny

• ISSUE-124: Futures / Order of parameters (was: Re: Request for JSON-LD API review) (Wednesday, 17 April)

Marcos Caceres

• Re: WebIDL generated TypeErrors and promises (Friday, 28 June)
• Re: WebIDL generated TypeErrors and promises (Friday, 28 June)
• Re: WebIDL generated TypeErrors and promises (Friday, 28 June)
• WebIDL generated TypeErrors and promises (Friday, 28 June)
• Re: Guidance on using sequences and arrays (Wednesday, 26 June)
• Re: Guidance on using sequences and arrays (Wednesday, 26 June)
• Re: Guidance on using sequences and arrays (Wednesday, 26 June)
• Guidance on using sequences and arrays (Wednesday, 26 June)
• Re: Specs and Object.observe() (Monday, 17 June)
• Specs and Object.observe() (Monday, 17 June)
• Re: Please review Contacts Manager API. (Thursday, 6 June)
• Please review Contacts Manager API. (Thursday, 6 June)
• Re: Web Alarm API - idiomatic check (Thursday, 9 May)
• Re: Web Alarm API - idiomatic check (Thursday, 9 May)
• Re: Web Alarm API - idiomatic check (Thursday, 9 May)
• Re: Web Alarm API - idiomatic check (Thursday, 9 May)
• Re: Web Alarm API - idiomatic check (Thursday, 9 May)
• Web Alarm API - idiomatic check (Wednesday, 8 May)
• Re: API updated to use Futures - request for review (Wednesday, 8 May)
• Re: API updated to use Futures - request for review (Sunday, 5 May)

Mark Miller

• Re: A Challenge Problem for Promise Designers (Sunday, 28 April)
• Re: A Challenge Problem for Promise Designers (Sunday, 28 April)
• Re: A Challenge Problem for Promise Designers (Saturday, 27 April)
• Re: A Challenge Problem for Promise Designers (Saturday, 27 April)
• Re: A Challenge Problem for Promise Designers (Saturday, 27 April)
• What Are We Arguing About? (was: Re: A Challenge Problem for Promise Designers) (Friday, 26 April)

Mark S. Miller

• Re: [promises] Difficulties with using constructors and promises together (Thursday, 20 June)
• Re: [promises] Difficulties with using constructors and promises together (Thursday, 20 June)
• Re: Specs and Object.observe() (Monday, 17 June)
• Re: Deprecating Future's .then() (Monday, 17 June)
• Re: Deprecating Future's .then() (Thursday, 6 June)
• Re: Deprecating Future's .then() (Thursday, 6 June)
• Re: Deprecating Future's .then() (Wednesday, 5 June)
• Re: Deprecating Future's .then() (Wednesday, 5 June)
• Re: Deprecating Future's .then() (Tuesday, 4 June)
• Re: Deprecating Future's .then() (Tuesday, 4 June)
• Re: Deprecating Future's .then() (Monday, 3 June)
• Re: Deprecating Future's .then() (Monday, 3 June)
• Re: Future feedback (Tuesday, 14 May)
• Re: The Paradox of Partial Parametricity (Friday, 10 May)
• Re: The Paradox of Partial Parametricity (Friday, 10 May)
• Re: The Paradox of Partial Parametricity (Friday, 10 May)
• The Paradox of Partial Parametricity (Friday, 10 May)
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? (Wednesday, 8 May)
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? (Monday, 6 May)
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? (Monday, 6 May)
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? (Monday, 6 May)
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? (Friday, 3 May)
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? (Thursday, 2 May)
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? (Thursday, 2 May)
• Re: Do futures represent a pipeline? (was Re: Future cancellation) (Wednesday, 1 May)
• Re: A Challenge Problem for Promise Designers (Sunday, 28 April)
• Re: A Challenge Problem for Promise Designers (Saturday, 27 April)
• Re: Futures (Saturday, 27 April)
• Re: Promises in E (was Re: A Challenge Problem for Promise Designers) (Friday, 26 April)
• Re: ES6,ES7,ES8 and beyond. A Proposed Roadmap. (Wednesday, 24 April)
• Re: Futures (Monday, 22 April)
• Re: Futures (Monday, 22 April)
• ES6,ES7,ES8 and beyond. A Proposed Roadmap. (Sunday, 21 April)
• Re: More flexibility in the ECMAScript part? (Thursday, 18 April)
• Re: Futures (was: Request for JSON-LD API review) (Wednesday, 17 April)
• Re: Futures (was: Request for JSON-LD API review) (Wednesday, 17 April)
• Re: Futures (was: Request for JSON-LD API review) (Wednesday, 17 April)
• Re: Coordination (was: ES6 Modules) (Friday, 12 April)
• Re: Structured clones (Wednesday, 10 April)

Markus Lanthaler

• RE: API updated to use Futures - request for review (Monday, 6 May)
• API updated to use Futures - request for review (Sunday, 5 May)
• RE: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? (Friday, 3 May)
• RE: RDF-ISSUE-125 Futures (was: Request for JSON-LD API review) (Wednesday, 17 April)
• RDF-ISSUE-125 Futures vs. callbacks (was: Re: Request for JSON-LD API review) (Wednesday, 17 April)
• Request for JSON-LD API review (was: Coordination) (Tuesday, 16 April)
• RE: APIs that overload numbers and strings (Monday, 15 April)

Mounir Lamouri

• Re: Web Alarm API - idiomatic check (Thursday, 16 May)
• Review Request: Raw Socket API (Wednesday, 15 May)
• Re: Web Alarm API - idiomatic check (Wednesday, 15 May)

Mountie Lee

• please review and comment for my draft (Thursday, 25 April)

Norbert Lindenberg

• Re: [Alarm API] Time zone handling (Friday, 10 May)
• Re: [Alarm API] Time zone handling (Thursday, 9 May)
• Re: [Alarm API] Time zone handling (Thursday, 9 May)
• [Alarm API] Time zone handling (Thursday, 9 May)
• Re: Futures (was: Request for JSON-LD API review) (Wednesday, 17 April)

Olli Pettay

• Re: Coordination (Saturday, 13 April)

Phillips, Addison

• RE: APIs that overload numbers and strings (Sunday, 14 April)

Rick Waldron

• Re: Reconciling handling of optional arguments and handling of default values across ES and webidl (Tuesday, 18 June)
• Re: Specs and Object.observe() (Monday, 17 June)
• Re: Specs and Object.observe() (Monday, 17 June)
• Re: Specs and Object.observe() (Monday, 17 June)
• Re: Specs and Object.observe() (Monday, 17 June)
• RE: A Challenge Problem for Promise Designers (was: Re: Futures) (Friday, 26 April)
• Re: Coordination (Monday, 15 April)
• Re: Coordination (Sunday, 14 April)
• Re: Coordination (Saturday, 13 April)
• Re: Coordination (Saturday, 13 April)
• Re: Coordination (was: ES6 Modules) (Saturday, 13 April)
• Re: Outreach? (was Coordination/ES6 Modules) (Saturday, 13 April)
• Re: Coordination (Friday, 12 April)
• Re: Coordination (was: ES6 Modules) (Friday, 12 April)
• Re: ES6 Modules (Monday, 8 April)
• Re: ES6 Modules (Monday, 8 April)
• Re: Catching exceptions (Tuesday, 2 April)
• Re: Catching exceptions (Tuesday, 2 April)

Rik Cabanier

• Re: undefined values in dictionaries (Wednesday, 12 June)
• Re: undefined values in dictionaries (Wednesday, 12 June)
• Re: undefined values in dictionaries (Wednesday, 12 June)

Robin Berjon

• Re: WebIDL generated TypeErrors and promises (Friday, 28 June)
• Re: FileList (and other Array-like types) (Thursday, 30 May)
• Re: FileList (and other Array-like types) (Thursday, 30 May)
• Re: [Alarm API] Time zone handling (Thursday, 9 May)
• Re: Futures (Wednesday, 17 April)
• Re: Coordination (Monday, 15 April)
• Re: Coordination (Monday, 15 April)
• Coordination (was: ES6 Modules) (Thursday, 11 April)

Ron Buckton

• RE: The Paradox of Partial Parametricity (Friday, 10 May)
• RE: Future cancellation (Wednesday, 1 May)
• RE: Future cancellation (Wednesday, 1 May)
• RE: Future cancellation (Wednesday, 1 May)
• Re: Future cancellation (Tuesday, 30 April)
• Future cancellation (Tuesday, 30 April)
• RE: A Challenge Problem for Promise Designers (Monday, 29 April)
• RE: A Challenge Problem for Promise Designers (Monday, 29 April)
• RE: A Challenge Problem for Promise Designers (Monday, 29 April)
• Re: A Challenge Problem for Promise Designers (Saturday, 27 April)
• RE: Futures (Friday, 26 April)
• RE: Futures (Wednesday, 24 April)
• RE: Futures (Tuesday, 23 April)
• Re: Futures (Tuesday, 23 April)
• RE: Futures (was: Request for JSON-LD API review) (Wednesday, 17 April)

Sam L'ecuyer

• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? (Thursday, 2 May)
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? (Thursday, 2 May)
• Re: Promise/Future: asynchrony in 'then' (Wednesday, 1 May)
• Re: Future cancellation (Tuesday, 30 April)
• Re: Future cancellation (Tuesday, 30 April)
• Re: A Challenge Problem for Promise Designers (Friday, 26 April)

Sam Tobin-Hochstadt

• Re: Deprecating Future's .then() (Tuesday, 4 June)
• Re: Deprecating Future's .then() (Tuesday, 4 June)
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? (Tuesday, 7 May)
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? (Monday, 6 May)
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? (Saturday, 4 May)
• Re: Coordination (was: ES6 Modules) (Saturday, 13 April)
• Re: ES6 Modules (Tuesday, 9 April)
• Re: ES6 Modules (Monday, 8 April)

Sean Hogan

• Re: Deprecating Future's .then() (Wednesday, 19 June)
• Re: Deprecating Future's .then() (Monday, 17 June)
• Re: Deprecating Future's .then() (Thursday, 6 June)
• Re: Deprecating Future's .then() (Thursday, 6 June)
• Re: Deprecating Future's .then() (Wednesday, 5 June)
• Re: Deprecating Future's .then() (Sunday, 2 June)
• Re: Deprecating Future's .then() (Monday, 20 May)
• Re: Deprecating Future's .then() (Monday, 20 May)
• Re: Deprecating Future's .then() (Monday, 20 May)
• Deprecating Future's .then() (Saturday, 18 May)
• Re: Future feedback (Friday, 17 May)
• Re: Future feedback (Thursday, 16 May)
• Re: Future feedback (Thursday, 16 May)
• Re: Future feedback (Thursday, 16 May)
• Re: Future feedback (Thursday, 16 May)
• Re: Future feedback (Thursday, 16 May)
• Re: Future feedback (Tuesday, 14 May)
• Re: Future feedback (Tuesday, 14 May)
• Re: Future feedback (Tuesday, 14 May)
• Re: Future feedback (Tuesday, 14 May)
• Re: Future feedback (Monday, 13 May)
• Future feedback (Wednesday, 8 May)

Tab Atkins Jr.

• Re: [webidl] Add a [Maplike] tag? (Thursday, 27 June)
• Re: [webidl] Add a [Maplike] tag? (Thursday, 27 June)
• Re: [webidl] Add a [Maplike] tag? (Thursday, 27 June)
• Re: [webidl] Add a [Maplike] tag? (Thursday, 27 June)
• Re: [webidl] Add a [Maplike] tag? (Thursday, 27 June)
• Re: [promises] Difficulties with using constructors and promises together (Thursday, 20 June)
• [promises] Difficulties with using constructors and promises together (Thursday, 20 June)
• Re: [promises] Difficulties with using constructors and promises together (Thursday, 20 June)
• Re: undefined values in dictionaries (Wednesday, 12 June)
• Re: [webidl] Add a [Maplike] tag? (Tuesday, 11 June)
• Re: [webidl] Add a [Maplike] tag? (Tuesday, 11 June)
• Re: Deprecating Future's .then() (Thursday, 6 June)
• Re: Deprecating Future's .then() (Monday, 3 June)
• Re: Deprecating Future's .then() (Monday, 3 June)
• Fwd: [webidl] Add a [Maplike] tag? (Thursday, 30 May)
• Re: Deprecating Future's .then() (Monday, 20 May)
• Re: Deprecating Future's .then() (Monday, 20 May)
• Re: Review Request: Raw Socket API (Sunday, 19 May)
• Re: Deprecating Future's .then() (Sunday, 19 May)
• Re: The Paradox of Partial Parametricity (Friday, 10 May)
• Re: The Paradox of Partial Parametricity (Friday, 10 May)
• Re: [Alarm API] Time zone handling (Friday, 10 May)
• Re: [Alarm API] Time zone handling (Thursday, 9 May)
• Re: Web Alarm API - idiomatic check (Wednesday, 8 May)
• Re: Web Alarm API - idiomatic check (Wednesday, 8 May)
• Re: Reconciling handling of optional arguments and handling of default values across ES and webidl (Wednesday, 8 May)
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? (Monday, 6 May)
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? (Monday, 6 May)
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? (Monday, 6 May)
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? (Friday, 3 May)
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? (Friday, 3 May)
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? (Thursday, 2 May)
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? (Thursday, 2 May)
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? (Thursday, 2 May)
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? (Thursday, 2 May)
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? (Thursday, 2 May)
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? (Thursday, 2 May)
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? (Thursday, 2 May)
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? (Thursday, 2 May)
• Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? (Thursday, 2 May)
• Re: Future cancellation (Wednesday, 1 May)
• Re: Future cancellation (Wednesday, 1 May)
• Re: Future cancellation (Wednesday, 1 May)
• Re: Future cancellation (Wednesday, 1 May)
• Re: Promise/Future: asynchrony in 'then' (Wednesday, 1 May)
• Re: Do futures represent a pipeline? (was Re: Future cancellation) (Wednesday, 1 May)
• Re: Future cancellation (Wednesday, 1 May)
• Re: Future cancellation (Wednesday, 1 May)
• Re: Future cancellation (Wednesday, 1 May)
• Re: A Challenge Problem for Promise Designers (Monday, 29 April)
• Re: A Challenge Problem for Promise Designers (Monday, 29 April)
• Re: A Challenge Problem for Promise Designers (Sunday, 28 April)
• Re: A Challenge Problem for Promise Designers (Saturday, 27 April)
• Re: A Challenge Problem for Promise Designers (Saturday, 27 April)
• Re: A Challenge Problem for Promise Designers (Saturday, 27 April)
• Re: A Challenge Problem for Promise Designers (Saturday, 27 April)
• Re: A Challenge Problem for Promise Designers (Saturday, 27 April)
• Re: A Challenge Problem for Promise Designers (Saturday, 27 April)
• Re: A Challenge Problem for Promise Designers (Friday, 26 April)
• Re: A Challenge Problem for Promise Designers (Friday, 26 April)
• Re: A Challenge Problem for Promise Designers (Friday, 26 April)
• Re: A Challenge Problem for Promise Designers (Friday, 26 April)
• Re: Futures (Friday, 26 April)
• Re: Futures (Friday, 26 April)
• Re: What Are We Arguing About? (was: Re: A Challenge Problem for Promise Designers) (Friday, 26 April)
• Re: Futures (Friday, 26 April)
• Re: What Are We Arguing About? (was: Re: A Challenge Problem for Promise Designers) (Friday, 26 April)
• Re: Futures (Friday, 26 April)
• Re: A Challenge Problem for Promise Designers (was: Re: Futures) (Friday, 26 April)
• Re: Futures (Friday, 26 April)
• Re: A Challenge Problem for Promise Designers (was: Re: Futures) (Friday, 26 April)
• Re: A Challenge Problem for Promise Designers (was: Re: Futures) (Friday, 26 April)
• Re: Futures (Tuesday, 23 April)
• Re: Futures (Tuesday, 23 April)
• Re: More flexibility in the ECMAScript part? (Thursday, 18 April)
• Re: Allowing IDL attributes to have different types for the getter and setter (Thursday, 18 April)
• Re: Futures (was: Request for JSON-LD API review) (Wednesday, 17 April)
• Re: Futures (Wednesday, 17 April)
• Re: ISSUE-124: Futures / Order of parameters (was: Re: Request for JSON-LD API review) (Wednesday, 17 April)
• Re: ISSUE-124: Futures / Order of parameters (was: Re: Request for JSON-LD API review) (Wednesday, 17 April)
• Re: ISSUE-124: Futures / Order of parameters (was: Re: Request for JSON-LD API review) (Wednesday, 17 April)
• Re: Futures (was: Request for JSON-LD API review) (Wednesday, 17 April)
• Re: Request for JSON-LD API review (was: Coordination) (Tuesday, 16 April)
• Re: Coordination (Monday, 15 April)
• Re: APIs that overload numbers and strings (Saturday, 13 April)
• Re: Coordination (Saturday, 13 April)

Till Schneidereit

• Re: ES6,ES7,ES8 and beyond. A Proposed Roadmap. (Wednesday, 24 April)
• Re: ES6,ES7,ES8 and beyond. A Proposed Roadmap. (Wednesday, 24 April)
• Re: ES6 Modules (Monday, 8 April)

Tom Van Cutsem

• Re: A Challenge Problem for Promise Designers (was: Re: Futures) (Wednesday, 22 May)
• Re: A Challenge Problem for Promise Designers (was: Re: Futures) (Monday, 20 May)

Yusuke SUZUKI

• Re: A new ES6 spec. draft has been posted (Wednesday, 15 May)

Last message date: Sunday, 30 June 2013 18:46:08 UTC