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

Sunday, 30 June 2013

• [Bug 22522] New: WebIDL, error handling, and promises bugzilla@jessica.w3.org

Saturday, 29 June 2013

• [Bug 22509] Some way to express array as readonly and fixed length bugzilla@jessica.w3.org
• Re: WebIDL generated TypeErrors and promises Boris Zbarsky
• [Bug 22509] Some way to express array as readonly and fixed length bugzilla@jessica.w3.org

Friday, 28 June 2013

• [Bug 22509] Some way to express array as readonly and fixed length bugzilla@jessica.w3.org
• [Bug 22509] Some way to express array as readonly and fixed length bugzilla@jessica.w3.org
• [Bug 22509] New: Some way to express array as readonly and fixed length bugzilla@jessica.w3.org
• Re: WebIDL generated TypeErrors and promises Robin Berjon
• Re: WebIDL generated TypeErrors and promises Marcos Caceres
• Re: WebIDL generated TypeErrors and promises Marcos Caceres
• RE: WebIDL generated TypeErrors and promises Domenic Denicola
• Re: WebIDL generated TypeErrors and promises Boris Zbarsky
• Re: WebIDL generated TypeErrors and promises Marcos Caceres
• Re: WebIDL generated TypeErrors and promises Boris Zbarsky
• Re: WebIDL generated TypeErrors and promises Boris Zbarsky
• Re: WebIDL generated TypeErrors and promises Domenic Denicola
• WebIDL generated TypeErrors and promises Marcos Caceres
• [Bug 22507] New: Need to define behaviour for setting properties on named properties objects bugzilla@jessica.w3.org
• [Bug 22506] New: Named properties object should probably not be a function object bugzilla@jessica.w3.org

Thursday, 27 June 2013

• Re: [webidl] Add a [Maplike] tag? Tab Atkins Jr.
• Re: [webidl] Add a [Maplike] tag? Boris Zbarsky
• Re: [webidl] Add a [Maplike] tag? Tab Atkins Jr.
• Re: [webidl] Add a [Maplike] tag? Boris Zbarsky
• Re: [webidl] Add a [Maplike] tag? Tab Atkins Jr.
• Re: [webidl] Add a [Maplike] tag? Boris Zbarsky
• Re: [webidl] Add a [Maplike] tag? Tab Atkins Jr.
• Re: [webidl] Add a [Maplike] tag? Tab Atkins Jr.
• [Bug 21422] Generic Promise type notation bugzilla@jessica.w3.org
• [Bug 21422] Generic Promise type notation bugzilla@jessica.w3.org
• [Bug 21422] Generic Promise type notation bugzilla@jessica.w3.org
• [Bug 21422] Generic Promise type notation bugzilla@jessica.w3.org
• Re: [webidl] Add a [Maplike] tag? Cameron McCormack

Wednesday, 26 June 2013

• Re: Guidance on using sequences and arrays Marcos Caceres
• Re: Guidance on using sequences and arrays Boris Zbarsky
• RE: Guidance on using sequences and arrays Domenic Denicola
• Re: Guidance on using sequences and arrays Boris Zbarsky
• Re: Guidance on using sequences and arrays Marcos Caceres
• Re: Guidance on using sequences and arrays Boris Zbarsky
• Re: Guidance on using sequences and arrays Marcos Caceres
• Re: Guidance on using sequences and arrays Boris Zbarsky
• Guidance on using sequences and arrays Marcos Caceres

Monday, 24 June 2013

• Re: undefined values in dictionaries Boris Zbarsky
• Re: undefined values in dictionaries Anne van Kesteren
• Re: Reconciling handling of optional arguments and handling of default values across ES and webidl Cameron McCormack
• Re: undefined values in dictionaries Boris Zbarsky

Sunday, 23 June 2013

• Re: undefined values in dictionaries Cameron McCormack

Thursday, 20 June 2013

• Re: [promises] Difficulties with using constructors and promises together Mark S. Miller
• Re: [promises] Difficulties with using constructors and promises together Tab Atkins Jr.
• Re: [promises] Difficulties with using constructors and promises together Mark S. Miller
• Re: [promises] Difficulties with using constructors and promises together François REMY
• [promises] Difficulties with using constructors and promises together Tab Atkins Jr.
• Re: [promises] Difficulties with using constructors and promises together Tab Atkins Jr.
• Re: [promises] Difficulties with using constructors and promises together Anne van Kesteren

Wednesday, 19 June 2013

• Re: Deprecating Future's .then() Sean Hogan

Tuesday, 18 June 2013

• Re: Reconciling handling of optional arguments and handling of default values across ES and webidl Rick Waldron
• Re: Reconciling handling of optional arguments and handling of default values across ES and webidl Boris Zbarsky
• Re: Reconciling handling of optional arguments and handling of default values across ES and webidl Allen Wirfs-Brock
• Re: Reconciling handling of optional arguments and handling of default values across ES and webidl Boris Zbarsky
• Re: Reconciling handling of optional arguments and handling of default values across ES and webidl Allen Wirfs-Brock
• Re: Reconciling handling of optional arguments and handling of default values across ES and webidl Allen Wirfs-Brock
• Re: undefined values in dictionaries Boris Zbarsky
• Re: Reconciling handling of optional arguments and handling of default values across ES and webidl Boris Zbarsky
• Re: undefined values in dictionaries Cameron McCormack
• Re: Reconciling handling of optional arguments and handling of default values across ES and webidl Cameron McCormack
• [Bug 22392] maybe define .name for Function objects corresponding to operations/attributes bugzilla@jessica.w3.org
• [Bug 22392] maybe define .name for Function objects corresponding to operations/attributes bugzilla@jessica.w3.org
• [Bug 22320] Form's supported property names should perhaps not be enumerable bugzilla@jessica.w3.org
• Re: Extended attributes on WebIDL typedefs need to be defined better, or just dropped Cameron McCormack
• [Bug 22392] maybe define .name for Function objects corresponding to operations/attributes bugzilla@jessica.w3.org
• [Bug 22392] maybe define .name for Function objects corresponding to operations/attributes bugzilla@jessica.w3.org
• Re: Off-by-one error in double to long long conversion ? Cameron McCormack

Monday, 17 June 2013

• [Bug 22320] Form's supported property names should perhaps not be enumerable bugzilla@jessica.w3.org
• [Bug 22392] New: maybe define .name for Function objects corresponding to operations/attributes bugzilla@jessica.w3.org
• Re: Specs and Object.observe() David Bruant
• [Bug 22391] New: Sequence or Array bugzilla@jessica.w3.org
• Re: Specs and Object.observe() Rick Waldron
• RE: Specs and Object.observe() Domenic Denicola
• Re: Specs and Object.observe() Rick Waldron
• Re: Specs and Object.observe() Mark S. Miller
• Re: Specs and Object.observe() Rick Waldron
• Re: Specs and Object.observe() Rick Waldron
• Re: Question about implements statements Boris Zbarsky
• Re: Question about implements statements Cameron McCormack
• Re: Question about implements statements Boris Zbarsky
• Re: Specs and Object.observe() Marcos Caceres
• Re: Specs and Object.observe() François REMY
• Specs and Object.observe() Marcos Caceres
• Re: WebIDL should define "native Array" Cameron McCormack
• Re: Question about implements statements Cameron McCormack
• [Bug 22358] Add a "this is the global" annotation bugzilla@jessica.w3.org
• [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 bugzilla@jessica.w3.org
• [Bug 22312] Typo? bugzilla@jessica.w3.org
• [Bug 22168] An attribute cannot be a dictionary type bugzilla@jessica.w3.org
• [Bug 22156] Allow trailing commas in Web IDL lists bugzilla@jessica.w3.org
• [Bug 21929] named properties object should disallow definition of non-configurable properties bugzilla@jessica.w3.org
• [Bug 21670] Clarify that typeof InterfaceObject should be "function" bugzilla@jessica.w3.org
• [Bug 21669] Callable interface objects should be instance of Function bugzilla@jessica.w3.org
• [Bug 21640] Dictionaries and callbacks should be distinguishable bugzilla@jessica.w3.org
• [Bug 21591] String constant on NavigatorID is invalid per WebIDL bugzilla@jessica.w3.org
• [Bug 21589] SelectionMode enum should not have a trailing comma bugzilla@jessica.w3.org
• [Bug 21295] overload resolution: are DOMString and sequence<T> distinguishable now? bugzilla@jessica.w3.org
• [Bug 20777] Getting a property from the global scope polluter ends up in an infinite loop bugzilla@jessica.w3.org
• [Bug 20653] Function object doesn't specify needing a "prototype" property bugzilla@jessica.w3.org
• [Bug 20561] Objects supporting indexed properties bugzilla@jessica.w3.org
• [Bug 20535] consider removing indexed property setters, creators and deleters bugzilla@jessica.w3.org
• [Bug 20528] Definition of [[Prototype]] for the interface prototype object is confusing bugzilla@jessica.w3.org
• [Bug 20527] Comment about NamedPropertiesObject is incorrect bugzilla@jessica.w3.org
• [Bug 20481] Grammar Fixes needed: Dominique's feedback + Microsoft's feedback bugzilla@jessica.w3.org
• [Bug 20478] Grammar allows "static;" as a valid operation bugzilla@jessica.w3.org
• [Bug 20475] Grammar allows "- Infinity", but not "- 1" bugzilla@jessica.w3.org
• [Bug 20458] 4.2.22: converting IDL value to IDL type? bugzilla@jessica.w3.org
• [Bug 20456] 4.2.24.1: wrong conversion bugzilla@jessica.w3.org
• [Bug 20455] converting to an ECMAScript value [of a specified type??] bugzilla@jessica.w3.org
• [Bug 20453] 3.1: two questions re underscore removal bugzilla@jessica.w3.org
• [Bug 20452] 4.2.16: extraneous "the" bugzilla@jessica.w3.org
• [Bug 20444] 4.*: "descriptor { ... }" bugzilla@jessica.w3.org
• [Bug 20443] 4.4.6: "is not of the enumeration’s values" bugzilla@jessica.w3.org
• [Bug 20442] 4.2.24: <ul> should be <ol> bugzilla@jessica.w3.org
• [Bug 20440] 4.4.1.1: "of it type list" bugzilla@jessica.w3.org
• [Bug 20439] 4.4.6: <span class="desc"> bugzilla@jessica.w3.org
• [Bug 20422] 4.2.21: "then then" bugzilla@jessica.w3.org
• [Bug 20419] 4.2.24.2: missing "then"? bugzilla@jessica.w3.org
• [Bug 20225] don't allow overridden operations and attribute getters/setters to be invoked on descendant objects bugzilla@jessica.w3.org
• [Bug 20008] allow [Unforgeable] on an interface bugzilla@jessica.w3.org
• [Bug 19988] add a [LenientFloat] to mean "ignore IDL attribute assignment or method call if a non-finite float is passed" bugzilla@jessica.w3.org
• [Bug 19936] consider allowing non-matching enums to be converted to a particular value bugzilla@jessica.w3.org
• [Bug 18908] Consider disallowing expandos on objects with a named getter but no named setter bugzilla@jessica.w3.org
• [Bug 18547] Add [ImplicitThis] to EventTarget? bugzilla@jessica.w3.org
• [Bug 18362] Make stringifiers not take into account expandos bugzilla@jessica.w3.org
• [Bug 18352] Note about Object.prototype.toString is unclear bugzilla@jessica.w3.org
• [Bug 17713] Exceptions thrown from event handlers should not be propagated bugzilla@jessica.w3.org
• [Bug 16833] consider always exposing a "length" property for objects with indexed properties bugzilla@jessica.w3.org
• [Bug 16767] Allow user objects for Array[] types bugzilla@jessica.w3.org
• Re: Deprecating Future's .then() Mark S. Miller
• [Bug 16604] RFE: add unsigned byte as synonym for octet bugzilla@jessica.w3.org
• [Bug 16537] Interface types - Implements is ambiguous bugzilla@jessica.w3.org
• [Bug 16455] Using platform object example bugzilla@jessica.w3.org
• Re: Deprecating Future's .then() Sean Hogan

Friday, 14 June 2013

• [Bug 22358] Add a "this is the global" annotation bugzilla@jessica.w3.org
• [Bug 22358] Add a "this is the global" annotation bugzilla@jessica.w3.org
• [Bug 22358] New: Add a "this is the global" annotation bugzilla@jessica.w3.org

Thursday, 13 June 2013

• [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 bugzilla@jessica.w3.org
• [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 bugzilla@jessica.w3.org
• Re: undefined values in dictionaries Cameron McCormack

Wednesday, 12 June 2013

• Re: undefined values in dictionaries Boris Zbarsky
• Re: undefined values in dictionaries Tab Atkins Jr.
• Re: undefined values in dictionaries Boris Zbarsky
• Re: undefined values in dictionaries Rik Cabanier
• Re: undefined values in dictionaries Boris Zbarsky
• Re: undefined values in dictionaries Rik Cabanier
• Re: undefined values in dictionaries Boris Zbarsky
• Re: undefined values in dictionaries Boris Zbarsky
• Re: undefined values in dictionaries Brendan Eich
• Re: undefined values in dictionaries Rik Cabanier
• Re: undefined values in dictionaries Jonas Sicking

Tuesday, 11 June 2013

• undefined values in dictionaries Boris Zbarsky
• Re: [webidl] Add a [Maplike] tag? Tab Atkins Jr.
• Re: [webidl] Add a [Maplike] tag? Tab Atkins Jr.

Monday, 10 June 2013

• Re: Request for API design feedback: Web MIDI API Anne van Kesteren

Saturday, 8 June 2013

• Request for API design feedback: Web MIDI API Jussi Kalliokoski
• [Bug 22312] New: Typo? bugzilla@jessica.w3.org
• Re: [Futures] accept/resolve/reject on a resolver don't have clearly defined behavior if no value is passed Cameron McCormack

Friday, 7 June 2013

• Re: [Futures] accept/resolve/reject on a resolver don't have clearly defined behavior if no value is passed Jonas Sicking
• Re: [Futures] accept/resolve/reject on a resolver don't have clearly defined behavior if no value is passed Boris Zbarsky
• Re: resolving references when object from other security context is in scope Boris Zbarsky
• Re: resolving references when object from other security context is in scope Hallvord Reiar Michaelsen Steen
• Re: [Futures] accept/resolve/reject on a resolver don't have clearly defined behavior if no value is passed Brendan Eich
• resolving references when object from other security context is in scope Hallvord Reiar M. Steen

Thursday, 6 June 2013

• Re: [Futures] accept/resolve/reject on a resolver don't have clearly defined behavior if no value is passed Boris Zbarsky
• Re: Please review Contacts Manager API. Marcos Caceres
• Please review Contacts Manager API. Marcos Caceres
• Re: Deprecating Future's .then() Mark S. Miller
• Re: Deprecating Future's .then() Sean Hogan
• Re: Deprecating Future's .then() Mark S. Miller
• Re: Deprecating Future's .then() Tab Atkins Jr.
• Re: Deprecating Future's .then() Sean Hogan

Wednesday, 5 June 2013

• Re: Deprecating Future's .then() Mark S. Miller
• Re: Deprecating Future's .then() Sean Hogan
• Re: Deprecating Future's .then() Anne van Kesteren
• Re: Deprecating Future's .then() Mark S. Miller
• Re: Deprecating Future's .then() Anne van Kesteren
• Re: Deprecating Future's .then() Anne van Kesteren
• Re: Deprecating Future's .then() Alex Russell

Tuesday, 4 June 2013

• Re: Deprecating Future's .then() Mark S. Miller
• Re: Deprecating Future's .then() Mark S. Miller
• RE: Deprecating Future's .then() Domenic Denicola
• Re: Deprecating Future's .then() Sam Tobin-Hochstadt
• Re: Deprecating Future's .then() Anne van Kesteren
• Re: Deprecating Future's .then() Sam Tobin-Hochstadt

Monday, 3 June 2013

• Re: Deprecating Future's .then() Mark S. Miller
• Re: Deprecating Future's .then() Tab Atkins Jr.
• Re: Deprecating Future's .then() Anne van Kesteren
• Re: Deprecating Future's .then() Mark S. Miller
• Re: Deprecating Future's .then() Tab Atkins Jr.
• Re: Deprecating Future's .then() Anne van Kesteren

Sunday, 2 June 2013

• Re: Deprecating Future's .then() Sean Hogan

Saturday, 1 June 2013

• Re: [webidl] Section on serializer ES bindings has copy/paste "stringifier" Cameron McCormack
• [webidl] Section on serializer ES bindings has copy/paste "stringifier" Boris Zbarsky

Thursday, 30 May 2013

• Re: Fwd: [webidl] Add a [Maplike] tag? Boris Zbarsky
• Fwd: [webidl] Add a [Maplike] tag? Tab Atkins Jr.
• Re: FileList (and other Array-like types) Robin Berjon
• Re: FileList (and other Array-like types) Boris Zbarsky
• Re: FileList (and other Array-like types) Robin Berjon
• Re: FileList (and other Array-like types) Boris Zbarsky
• Re: FileList (and other Array-like types) Jonas Sicking
• Re: FileList (and other Array-like types) Boris Zbarsky
• FileList (and other Array-like types) Jonas Sicking

Tuesday, 28 May 2013

• [Bug 22168] An attribute cannot be a dictionary type bugzilla@jessica.w3.org
• [Bug 22168] An attribute cannot be a dictionary type bugzilla@jessica.w3.org
• RfC: 2nd Last Call of "Vibration API"; deadline June 13 Arthur Barstow

Monday, 27 May 2013

• [Bug 21591] String constant on NavigatorID is invalid per WebIDL bugzilla@jessica.w3.org

Sunday, 26 May 2013

• [Bug 22168] An attribute cannot be a dictionary type bugzilla@jessica.w3.org
• [Bug 22168] New: An attribute cannot be a dictionary type bugzilla@jessica.w3.org

Friday, 24 May 2013

• [Bug 21589] SelectionMode enum should not have a trailing comma bugzilla@jessica.w3.org
• [Bug 21589] SelectionMode enum should not have a trailing comma bugzilla@jessica.w3.org
• [Bug 21589] SelectionMode enum should not have a trailing comma bugzilla@jessica.w3.org
• [Bug 17508] Let enum lists end with a comma bugzilla@jessica.w3.org
• [Bug 22156] Allow trailing commas in Web IDL lists bugzilla@jessica.w3.org
• [Bug 21589] SelectionMode enum should not have a trailing comma bugzilla@jessica.w3.org
• [Bug 22156] New: Allow trailing commas in Web IDL lists bugzilla@jessica.w3.org
• [Bug 19778] Wrong regex for integer bugzilla@jessica.w3.org
• [Bug 19778] Wrong regex for integer bugzilla@jessica.w3.org

Wednesday, 22 May 2013

• Re: A Challenge Problem for Promise Designers (was: Re: Futures) Tom Van Cutsem

Tuesday, 21 May 2013

• Re: URL/URI APIs Anne van Kesteren
• Re: URL/URI APIs Bjoern Hoehrmann
• Re: A Challenge Problem for Promise Designers (was: Re: Futures) Andreas Rossberg

Monday, 20 May 2013

• Re: Deprecating Future's .then() Sean Hogan
• Re: Deprecating Future's .then() Tab Atkins Jr.
• Re: A Challenge Problem for Promise Designers (was: Re: Futures) Tom Van Cutsem
• Re: Future feedback Alex Russell
• Re: Deprecating Future's .then() Sean Hogan
• Re: Review Request: Raw Socket API Jonas Sicking
• Re: URL/URI APIs Garrett Smith
• Re: Deprecating Future's .then() Tab Atkins Jr.
• Re: Deprecating Future's .then() Sean Hogan

Sunday, 19 May 2013

• URL/URI APIs Charles McCathie Nevile
• Re: Review Request: Raw Socket API Tab Atkins Jr.
• Re: Deprecating Future's .then() Tab Atkins Jr.

Saturday, 18 May 2013

• Deprecating Future's .then() Sean Hogan

Friday, 17 May 2013

• Re: Future feedback Sean Hogan
• Re: Future feedback Boris Zbarsky

Thursday, 16 May 2013

• Re: Future feedback Sean Hogan
• Re: Future feedback Sean Hogan
• Re: Future feedback Boris Zbarsky
• Re: Web Alarm API - idiomatic check Mounir Lamouri
• Re: Future feedback Sean Hogan
• Re: Future feedback Boris Zbarsky
• RE: Future feedback Domenic Denicola
• Re: Future feedback Sean Hogan
• Re: Future feedback Boris Zbarsky
• Re: Future feedback Sean Hogan

Wednesday, 15 May 2013

• Re: Web Alarm API - idiomatic check Jonas Sicking
• Re: A new ES6 spec. draft has been posted Yusuke SUZUKI
• Review Request: Raw Socket API Mounir Lamouri
• Re: Web Alarm API - idiomatic check Mounir Lamouri
• Re: Future feedback David Bruant
• A new ES6 spec. draft has been posted Allen Wirfs-Brock
• Re: Future feedback Boris Zbarsky

Tuesday, 14 May 2013

• Re: Future feedback Mark S. Miller
• Re: Future feedback Sean Hogan
• Re: Future feedback Boris Zbarsky
• Re: Future feedback Jorge
• Re: Future feedback David Bruant
• Re: Future feedback Boris Zbarsky
• Re: Future feedback David Bruant
• Re: Future feedback David Bruant
• Re: Future feedback Jorge
• Re: Future feedback Jorge
• Re: Future feedback Boris Zbarsky
• Re: Future feedback Jonas Sicking
• Re: Future feedback Boris Zbarsky
• Re: Future feedback Sean Hogan
• Re: Future feedback Sean Hogan
• Re: Future feedback Sean Hogan

Monday, 13 May 2013

• Re: Interface prototype objects and ES6 @@toStringTag Allen Wirfs-Brock
• Re: Interface prototype objects and ES6 @@toStringTag Boris Zbarsky
• Re: Interface prototype objects and ES6 @@toStringTag Erik Arvidsson
• Re: Interface prototype objects and ES6 @@toStringTag Allen Wirfs-Brock
• Re: Interface prototype objects and ES6 @@toStringTag Kevin Reid
• Re: Interface prototype objects and ES6 @@toStringTag Erik Arvidsson
• Re: Interface prototype objects and ES6 @@toStringTag Allen Wirfs-Brock
• Interface prototype objects and ES6 @@toStringTag Erik Arvidsson
• test suite for Web IDL v1 Cameron McCormack
• Re: Future feedback Jonas Sicking
• Re: Future feedback Boris Zbarsky
• Re: Future feedback Sean Hogan

Sunday, 12 May 2013

• [Bug 22014] newly created exception objects should have the exception prototype interface object as their [[Prototype]] bugzilla@jessica.w3.org
• [Bug 22014] New: newly created exception objects should have the exception prototype interface object as their [[Prototype]] bugzilla@jessica.w3.org
• [Bug 22013] property enumeration section should mention named property visibility bugzilla@jessica.w3.org
• [Bug 22013] New: property enumeration section should mention named property visibility bugzilla@jessica.w3.org

Saturday, 11 May 2013

• [Bug 22006] need to define that the .length of a stringifier's Function object is 0 bugzilla@jessica.w3.org
• [Bug 22006] New: need to define that the .length of a stringifier's Function object is 0 bugzilla@jessica.w3.org

Friday, 10 May 2013

• Webapps face to face meeting summary Charles McCathie Nevile
• Re: The Paradox of Partial Parametricity Tab Atkins Jr.
• Re: The Paradox of Partial Parametricity Andreas Rossberg
• Re: Future feedback David Bruant
• RE: The Paradox of Partial Parametricity Ron Buckton
• Re: The Paradox of Partial Parametricity Andreas Rossberg
• Re: The Paradox of Partial Parametricity Tab Atkins Jr.
• Re: The Paradox of Partial Parametricity Mark S. Miller
• Re: The Paradox of Partial Parametricity Kevin Smith
• Re: The Paradox of Partial Parametricity Mark S. Miller
• Re: The Paradox of Partial Parametricity Mark S. Miller
• The Paradox of Partial Parametricity Mark S. Miller
• Re: Reconciling handling of optional arguments and handling of default values across ES and webidl Jonas Sicking
• Re: Reconciling handling of optional arguments and handling of default values across ES and webidl Boris Zbarsky
• Re: [Alarm API] Time zone handling Jonas Sicking
• Re: [Alarm API] Time zone handling Jonas Sicking
• Re: Reconciling handling of optional arguments and handling of default values across ES and webidl Boris Zbarsky
• Re: [Alarm API] Time zone handling Jonas Sicking
• Re: [Alarm API] Time zone handling Tab Atkins Jr.
• Re: [Alarm API] Time zone handling Norbert Lindenberg
• Re: [Alarm API] Time zone handling Jonas Sicking
• Re: [Alarm API] Time zone handling Jonas Sicking

Thursday, 9 May 2013

• Re: [Alarm API] Time zone handling Norbert Lindenberg
• Re: [Alarm API] Time zone handling Tab Atkins Jr.
• Re: [Alarm API] Time zone handling Norbert Lindenberg
• Re: [Alarm API] Time zone handling Jonas Sicking
• Re: Reconciling handling of optional arguments and handling of default values across ES and webidl Garrett Smith
• RE: Web Alarm API - idiomatic check Christophe Dumez - SISA
• Re: Web Alarm API - idiomatic check Marcos Caceres
• Re: Web Alarm API - idiomatic check Marcos Caceres
• Re: Web Alarm API - idiomatic check Marcos Caceres
• Re: Web Alarm API - idiomatic check Marcos Caceres
• Re: Web Alarm API - idiomatic check Marcos Caceres
• Re: Reconciling handling of optional arguments and handling of default values across ES and webidl Boris Zbarsky
• Re: Reconciling handling of optional arguments and handling of default values across ES and webidl Garrett Smith
• Re: [Alarm API] Time zone handling Robin Berjon
• Re: Reconciling handling of optional arguments and handling of default values across ES and webidl Boris Zbarsky
• Re: Reconciling handling of optional arguments and handling of default values across ES and webidl Andreas Rossberg

Wednesday, 8 May 2013

• Re: Reconciling handling of optional arguments and handling of default values across ES and webidl Brandon Benvie
• Re: Reconciling handling of optional arguments and handling of default values across ES and webidl Brandon Benvie

Thursday, 9 May 2013

• Re: Reconciling handling of optional arguments and handling of default values across ES and webidl Boris Zbarsky
• Re: Reconciling handling of optional arguments and handling of default values across ES and webidl Andreas Rossberg
• Re: Future feedback Alex Russell
• Re: Reconciling handling of optional arguments and handling of default values across ES and webidl Boris Zbarsky
• [Alarm API] Time zone handling Norbert Lindenberg
• Re: Reconciling handling of optional arguments and handling of default values across ES and webidl Allen Wirfs-Brock
• Re: Reconciling handling of optional arguments and handling of default values across ES and webidl Boris Zbarsky
• Re: Reconciling handling of optional arguments and handling of default values across ES and webidl Boris Zbarsky
• Re: Reconciling handling of optional arguments and handling of default values across ES and webidl Boris Zbarsky

Wednesday, 8 May 2013

• Re: Reconciling handling of optional arguments and handling of default values across ES and webidl Garrett Smith
• Re: Web Alarm API - idiomatic check Jonas Sicking
• Re: Web Alarm API - idiomatic check Allen Wirfs-Brock
• Re: Reconciling handling of optional arguments and handling of default values across ES and webidl Allen Wirfs-Brock
• Re: Reconciling handling of optional arguments and handling of default values across ES and webidl Boris Zbarsky
• Re: Web Alarm API - idiomatic check Jonas Sicking
• RE: Reconciling handling of optional arguments and handling of default values across ES and webidl Domenic Denicola
• Re: Reconciling handling of optional arguments and handling of default values across ES and webidl Jonas Sicking
• Re: Web Alarm API - idiomatic check Jorge
• Re: Web Alarm API - idiomatic check Joshua Bell
• Re: Web Alarm API - idiomatic check Jorge
• Re: Web Alarm API - idiomatic check Jake Verbaten
• Re: Web Alarm API - idiomatic check Jake Verbaten
• Re: [Future] First arguments should not be optional Garrett Smith
• Re: Web Alarm API - idiomatic check Tab Atkins Jr.
• Re: Web Alarm API - idiomatic check Jake Verbaten
• Re: Web Alarm API - idiomatic check Tab Atkins Jr.
• Re: Web Alarm API - idiomatic check Allen Wirfs-Brock
• Re: Reconciling handling of optional arguments and handling of default values across ES and webidl Tab Atkins Jr.
• Reconciling handling of optional arguments and handling of default values across ES and webidl Boris Zbarsky
• RE: Web Alarm API - idiomatic check Domenic Denicola
• Re: [Future] First arguments should not be optional Boris Zbarsky
• Re: Web Alarm API - idiomatic check Jake Verbaten
• Web Alarm API - idiomatic check Marcos Caceres
• [Bug 21422] Futures bugzilla@jessica.w3.org
• Re: API updated to use Futures - request for review Marcos Caceres
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? David Sheets
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? Jonas Sicking
• Re: Future feedback Boris Zbarsky
• Future feedback Sean Hogan
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? David Sheets
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? Mark S. Miller

Tuesday, 7 May 2013

• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? Jonas Sicking
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? Sam Tobin-Hochstadt
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? David Sheets
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? Jonas Sicking

Monday, 6 May 2013

• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? Mark S. Miller
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? Tab Atkins Jr.
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? Mark S. Miller
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? Tab Atkins Jr.
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? Jonas Sicking
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? Tab Atkins Jr.
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? Sam Tobin-Hochstadt
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? Mark S. Miller
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? Jonas Sicking
• Why is [Constructor] not allowed on partial interfaces? Boris Zbarsky
• RE: API updated to use Futures - request for review Markus Lanthaler

Sunday, 5 May 2013

• Re: API updated to use Futures - request for review Marcos Caceres
• API updated to use Futures - request for review Markus Lanthaler
• [Bug 21929] New: named properties object should disallow definition of non-configurable properties bugzilla@jessica.w3.org

Saturday, 4 May 2013

• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? Sam Tobin-Hochstadt

Friday, 3 May 2013

• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? Jonas Sicking
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? Tab Atkins Jr.
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? Tab Atkins Jr.
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? Alex Russell
• RE: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? Markus Lanthaler
• RE: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? Domenic Denicola
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? Mark S. Miller

Thursday, 2 May 2013

• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? Tab Atkins Jr.
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? Tab Atkins Jr.
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? Mark S. Miller
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? Jonas Sicking
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? Tab Atkins Jr.
• RE: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? Domenic Denicola
• RE: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? Domenic Denicola
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? Tab Atkins Jr.
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? Jonas Sicking
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? Sam L'ecuyer
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? Tab Atkins Jr.
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? Sam L'ecuyer
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? Tab Atkins Jr.
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? Mark S. Miller
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? Tab Atkins Jr.
• RE: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? Domenic Denicola
• Re: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? Tab Atkins Jr.
• RE: Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? Domenic Denicola
• Promises: Auto-assimilating thenables returned by .then() callbacks: yay/nay? Tab Atkins Jr.
• Re: Future cancellation Anne van Kesteren
• Re: Future cancellation Bill Frantz
• Re: Future cancellation Anne van Kesteren
• Re: Future cancellation Bill Frantz

Wednesday, 1 May 2013

• Re: Future cancellation Tab Atkins Jr.
• Re: Future cancellation Bill Frantz
• RE: Future cancellation Ron Buckton
• Re: Do futures represent a pipeline? (was Re: Future cancellation) Mark S. Miller
• RE: Future cancellation Domenic Denicola
• Re: Future cancellation Tab Atkins Jr.
• Re: Future cancellation Kevin Smith
• Re: Future cancellation Tab Atkins Jr.
• Re: Future cancellation Tab Atkins Jr.
• Re: Future cancellation Bill Frantz
• Re: Do futures represent a pipeline? (was Re: Future cancellation) Kris Kowal
• Re: Future cancellation Jonas Sicking
• RE: Promise/Future: asynchrony in 'then' Domenic Denicola
• Re: Promise/Future: asynchrony in 'then' Sam L'ecuyer
• Re: Promise/Future: asynchrony in 'then' Tab Atkins Jr.
• Re: Do futures represent a pipeline? (was Re: Future cancellation) Tab Atkins Jr.
• Re: Promise/Future: asynchrony in 'then' Alex Russell
• Re: Future cancellation Tab Atkins Jr.
• Re: Future cancellation Bjoern Hoehrmann
• Re: Future cancellation Tab Atkins Jr.
• Re: Future cancellation Juan Ignacio Dopazo
• Re: Future cancellation Kevin Smith
• Re: Future cancellation Bill Frantz
• Re: Future cancellation Anne van Kesteren
• Re: Future cancellation Alex Russell
• Re: Future cancellation Alex Russell
• Re: Future cancellation Jonas Sicking
• Re: Future cancellation Tab Atkins Jr.
• Re: Future cancellation Kevin Gadd
• RE: Future cancellation Domenic Denicola
• RE: Future cancellation Ron Buckton
• Re: Future cancellation Kevin Gadd
• RE: Future cancellation Domenic Denicola
• Re: Future cancellation Jonas Sicking
• Re: Future cancellation Jonas Sicking
• Re: Future cancellation Jonas Sicking
• Re: Future cancellation Bjoern Hoehrmann
• RE: Future cancellation Ron Buckton

Tuesday, 30 April 2013

• Re: Future cancellation Jonas Sicking
• Do futures represent a pipeline? (was Re: Future cancellation) Kevin Gadd
• Re: Future cancellation Kevin Gadd
• Re: Future cancellation Kevin Gadd
• Re: Future cancellation Kevin Smith
• Re: Future cancellation Sam L'ecuyer
• Re: Future cancellation Ron Buckton
• Re: Future cancellation Sam L'ecuyer
• Re: Future cancellation Juan Ignacio Dopazo
• Re: Future cancellation Lucas Smith
• Re: Future cancellation Brendan Eich
• Re: Future cancellation Alex Russell
• Future cancellation Ron Buckton

Monday, 29 April 2013

• RE: A Challenge Problem for Promise Designers Ron Buckton
• Re: A Challenge Problem for Promise Designers Tab Atkins Jr.
• RE: A Challenge Problem for Promise Designers Ron Buckton
• Re: A Challenge Problem for Promise Designers Tab Atkins Jr.
• RE: A Challenge Problem for Promise Designers Ron Buckton
• Fwd: CfC: publish Java bindings for WebIDL as a WG Note; deadline May 4 Arthur Barstow
• Re: What Are We Arguing About? (was: Re: A Challenge Problem for Promise Designers) Andreas Rossberg

Sunday, 28 April 2013

• Re: A Challenge Problem for Promise Designers Tab Atkins Jr.
• Re: A Challenge Problem for Promise Designers David Sheets
• Re: A Challenge Problem for Promise Designers David Sheets
• Re: A Challenge Problem for Promise Designers Mark S. Miller
• Re: A Challenge Problem for Promise Designers Mark Miller
• Re: A Challenge Problem for Promise Designers Mark Miller

Saturday, 27 April 2013

• Re: A Challenge Problem for Promise Designers Tab Atkins Jr.
• Re: A Challenge Problem for Promise Designers Dean Landolt
• Fwd: A Challenge Problem for Promise Designers David Sheets
• Re: A Challenge Problem for Promise Designers Tab Atkins Jr.

Friday, 26 April 2013

• Promises in E (was Re: A Challenge Problem for Promise Designers) Bill Frantz
• Re: Promises in E (was Re: A Challenge Problem for Promise Designers) Bill Frantz

Saturday, 27 April 2013

• Re: A Challenge Problem for Promise Designers Mark Miller
• Re: A Challenge Problem for Promise Designers Tab Atkins Jr.
• Re: A Challenge Problem for Promise Designers Mark S. Miller
• Re: A Challenge Problem for Promise Designers David Sheets
• Re: A Challenge Problem for Promise Designers Tab Atkins Jr.
• Re: A Challenge Problem for Promise Designers Mark Miller
• Re: A Challenge Problem for Promise Designers Tab Atkins Jr.
• Re: A Challenge Problem for Promise Designers Tab Atkins Jr.
• Re: A Challenge Problem for Promise Designers Ron Buckton
• Re: A Challenge Problem for Promise Designers Mark Miller
• Re: Futures Mark S. Miller
• Re: Futures Alex Russell

Friday, 26 April 2013

• RE: Futures Ron Buckton
• Re: A Challenge Problem for Promise Designers Tab Atkins Jr.
• Re: A Challenge Problem for Promise Designers Sam L'ecuyer
• Re: A Challenge Problem for Promise Designers Tab Atkins Jr.
• RE: A Challenge Problem for Promise Designers Domenic Denicola
• Re: A Challenge Problem for Promise Designers Tab Atkins Jr.
• Re: A Challenge Problem for Promise Designers Tab Atkins Jr.
• Re: A Challenge Problem for Promise Designers David Bruant
• Re: Futures Tab Atkins Jr.
• Re: Futures Kevin Smith
• Re: A Challenge Problem for Promise Designers Dean Landolt
• RE: A Challenge Problem for Promise Designers Domenic Denicola
• RE: Futures Domenic Denicola
• Re: Futures Kevin Smith
• Re: A Challenge Problem for Promise Designers David Bruant
• Re: What Are We Arguing About? (was: Re: A Challenge Problem for Promise Designers) David Bruant
• RE: Futures Domenic Denicola
• Re: Futures Tab Atkins Jr.
• Re: Futures Juan Ignacio Dopazo
• Re: Futures Alex Russell
• Re: What Are We Arguing About? (was: Re: A Challenge Problem for Promise Designers) Tab Atkins Jr.
• Re: Futures Kevin Smith
• Re: What Are We Arguing About? (was: Re: A Challenge Problem for Promise Designers) Juan Ignacio Dopazo
• Re: Futures Juan Ignacio Dopazo
• Re: Futures Anne van Kesteren
• Re: Futures Kevin Smith
• Re: Futures Anne van Kesteren
• Re: Futures Juan Ignacio Dopazo
• RE: What Are We Arguing About? (was: Re: A Challenge Problem for Promise Designers) Domenic Denicola
• RE: A Challenge Problem for Promise Designers (was: Re: Futures) Rick Waldron
• Re: Futures Tab Atkins Jr.
• Re: What Are We Arguing About? (was: Re: A Challenge Problem for Promise Designers) Tab Atkins Jr.
• Re: Futures Kevin Smith
• Re: What Are We Arguing About? (was: Re: A Challenge Problem for Promise Designers) David Bruant
• Re: Futures Tab Atkins Jr.
• Re: Futures Kevin Smith
• Re: A Challenge Problem for Promise Designers (was: Re: Futures) Tab Atkins Jr.
• Re: Futures Tab Atkins Jr.
• RE: A Challenge Problem for Promise Designers (was: Re: Futures) Domenic Denicola
• Re: A Challenge Problem for Promise Designers David Bruant
• Re: A Challenge Problem for Promise Designers (was: Re: Futures) Tab Atkins Jr.
• Re: Promises in E (was Re: A Challenge Problem for Promise Designers) Mark S. Miller
• Re: Futures David Sheets
• What Are We Arguing About? (was: Re: A Challenge Problem for Promise Designers) Mark Miller
• Re: A Challenge Problem for Promise Designers (was: Re: Futures) David Sheets
• Re: A Challenge Problem for Promise Designers (was: Re: Futures) Tab Atkins Jr.
• Re: A Challenge Problem for Promise Designers Andreas Rossberg
• RE: A Challenge Problem for Promise Designers (was: Re: Futures) Domenic Denicola
• Re: A Challenge Problem for Promise Designers (was: Re: Futures) David Sheets
• Re: A Challenge Problem for Promise Designers (was: Re: Futures) Kevin Smith
• RE: A Challenge Problem for Promise Designers (was: Re: Futures) Domenic Denicola
• Re: A Challenge Problem for Promise Designers Dean Landolt
• Re: A Challenge Problem for Promise Designers (was: Re: Futures) David Sheets
• Re: A Challenge Problem for Promise Designers (was: Re: Futures) David Sheets
• Re: A Challenge Problem for Promise Designers (was: Re: Futures) Juan Ignacio Dopazo
• Re: A Challenge Problem for Promise Designers Andreas Rossberg
• Re: A Challenge Problem for Promise Designers David Bruant
• Re: A Challenge Problem for Promise Designers (was: Re: Futures) Kevin Smith
• Re: A Challenge Problem for Promise Designers (was: Re: Futures) Alex Russell
• Re: A Challenge Problem for Promise Designers (was: Re: Futures) Kevin Smith
• Re: A Challenge Problem for Promise Designers David Bruant
• Re: A Challenge Problem for Promise Designers (was: Re: Futures) Andreas Rossberg
• Re: A Challenge Problem for Promise Designers (was: Re: Futures) David Bruant

Thursday, 25 April 2013

• Re: please review and comment for my draft David Bruant
• please review and comment for my draft Mountie Lee

Wednesday, 24 April 2013

• RE: Futures Ron Buckton
• Re: Futures Juan Ignacio Dopazo
• Re: ES6,ES7,ES8 and beyond. A Proposed Roadmap. Till Schneidereit
• Re: ES6,ES7,ES8 and beyond. A Proposed Roadmap. Mark S. Miller
• Re: ES6,ES7,ES8 and beyond. A Proposed Roadmap. David Bruant
• Re: ES6,ES7,ES8 and beyond. A Proposed Roadmap. Dean Landolt
• Re: Futures (was: Request for JSON-LD API review) Anne van Kesteren
• Re: ES6,ES7,ES8 and beyond. A Proposed Roadmap. Anne van Kesteren
• Re: ES6,ES7,ES8 and beyond. A Proposed Roadmap. Till Schneidereit

Tuesday, 23 April 2013

• RE: Futures Ron Buckton
• Re: Futures Ron Buckton

Wednesday, 24 April 2013

• Re: Futures David Bruant
• Re: Futures Alex Russell
• Re: Futures Alex Russell

Tuesday, 23 April 2013

• Re: Futures Tab Atkins Jr.
• Re: Futures David Sheets
• Re: Futures Tab Atkins Jr.
• Re: Futures Dean Landolt
• Re: Futures David Bruant
• Re: Futures Dean Landolt
• Re: Futures David Bruant
• Re: Futures Dean Landolt
• Re: Futures David Bruant
• [Bug 20019] Support subclassing ES6 Map bugzilla@jessica.w3.org

Monday, 22 April 2013

• Re: Futures Dean Landolt
• Re: Futures Kevin Smith
• Re: Futures Dean Landolt
• Re: Futures Dean Landolt
• Re: Futures David Bruant
• Re: Futures Kevin Smith
• Re: Futures Dean Landolt
• Re: Futures Mark S. Miller
• RE: Futures Domenic Denicola
• Re: Futures Dean Landolt
• Re: Futures David Bruant
• Re: Futures Mark S. Miller
• Re: Futures David Bruant
• Re: Futures David Bruant
• Re: Futures Anne van Kesteren
• Re: Futures Kevin Smith
• Re: Futures David Bruant
• Re: Futures Kevin Smith
• Re: Futures Anne van Kesteren

Sunday, 21 April 2013

• ES6,ES7,ES8 and beyond. A Proposed Roadmap. Mark S. Miller
• Re: Futures Kevin Smith

Saturday, 20 April 2013

• Re: Futures Jonas Sicking
• Re: Futures Brendan Eich
• Re: Futures Brendan Eich
• Re: Futures Brendan Eich

Friday, 19 April 2013

• Re: Futures (was: Request for JSON-LD API review) Alex Russell

Thursday, 18 April 2013

• Re: More flexibility in the ECMAScript part? Tab Atkins Jr.
• Re: More flexibility in the ECMAScript part? Kevin Smith
• Re: More flexibility in the ECMAScript part? Mark S. Miller
• Re: More flexibility in the ECMAScript part? David Bruant
• Re: Futures (was: Request for JSON-LD API review) Anne van Kesteren
• Re: Futures (was: Request for JSON-LD API review) Jorge
• Re: More flexibility in the ECMAScript part? Jorge

Wednesday, 17 April 2013

• RE: Futures (was: Request for JSON-LD API review) Ron Buckton

Thursday, 18 April 2013

• Re: Allowing IDL attributes to have different types for the getter and setter David Bruant
• Re: Allowing IDL attributes to have different types for the getter and setter Boris Zbarsky
• Re: Allowing IDL attributes to have different types for the getter and setter Allen Wirfs-Brock
• RE: Allowing IDL attributes to have different types for the getter and setter Domenic Denicola
• Re: Allowing IDL attributes to have different types for the getter and setter Boris Zbarsky
• Re: Allowing IDL attributes to have different types for the getter and setter Tab Atkins Jr.
• Re: Allowing IDL attributes to have different types for the getter and setter Boris Zbarsky
• RE: Allowing IDL attributes to have different types for the getter and setter Domenic Denicola
• Allowing IDL attributes to have different types for the getter and setter Boris Zbarsky

Wednesday, 17 April 2013

• Re: Futures (was: Request for JSON-LD API review) Tab Atkins Jr.
• Re: Futures (was: Request for JSON-LD API review) Kevin Smith
• Re: Futures Tab Atkins Jr.
• Re: Futures Boris Zbarsky
• Re: ISSUE-124: Futures / Order of parameters (was: Re: Request for JSON-LD API review) Tab Atkins Jr.
• Re: ISSUE-124: Futures / Order of parameters (was: Re: Request for JSON-LD API review) Tab Atkins Jr.
• Re: ISSUE-124: Futures / Order of parameters (was: Re: Request for JSON-LD API review) Tab Atkins Jr.
• Re: Futures Alex Russell
• Re: Futures Robin Berjon
• Re: Futures (was: Request for JSON-LD API review) Anne van Kesteren
• Re: Futures (was: Request for JSON-LD API review) Anne van Kesteren
• Re: Futures (was: Request for JSON-LD API review) Mark S. Miller
• Re: Futures (was: Request for JSON-LD API review) Anne van Kesteren
• Re: Futures (was: Request for JSON-LD API review) Tab Atkins Jr.
• Re: Futures (was: Request for JSON-LD API review) Mark S. Miller
• Re: Futures (was: Request for JSON-LD API review) Mark S. Miller
• RE: RDF-ISSUE-125 Futures (was: Request for JSON-LD API review) Markus Lanthaler
• RDF-ISSUE-125 Futures vs. callbacks (was: Re: Request for JSON-LD API review) Markus Lanthaler
• ISSUE-124: Futures / Order of parameters (was: Re: Request for JSON-LD API review) Manu Sporny
• Re: Futures (was: Request for JSON-LD API review) Norbert Lindenberg

Tuesday, 16 April 2013

• Re: Request for JSON-LD API review (was: Coordination) Tab Atkins Jr.
• Request for JSON-LD API review (was: Coordination) Markus Lanthaler

Monday, 15 April 2013

• [Bug 21591] String constant on NavigatorID is invalid per WebIDL bugzilla@jessica.w3.org
• Re: Coordination Aymeric Vitte
• RE: APIs that overload numbers and strings Markus Lanthaler
• Re: APIs that overload numbers and strings Ehsan Akhgari
• Re: Coordination Allen Wirfs-Brock
• Re: APIs that overload numbers and strings Anne van Kesteren
• Re: APIs that overload numbers and strings Ehsan Akhgari
• Re: Coordination Allen Wirfs-Brock
• Re: APIs that overload numbers and strings Allen Wirfs-Brock
• Re: APIs that overload numbers and strings Allen Wirfs-Brock
• Re: APIs that overload numbers and strings Boris Zbarsky
• Re: APIs that overload numbers and strings Boris Zbarsky
• Re: Coordination Tab Atkins Jr.
• Re: APIs that overload numbers and strings Boris Zbarsky
• Re: Coordination Rick Waldron
• Re: Coordination Arthur Barstow
• Re: Coordination Charles McCathie Nevile
• Re: Coordination Robin Berjon
• Re: Coordination Robin Berjon
• Re: APIs that overload numbers and strings Ehsan Akhgari

Sunday, 14 April 2013

• RE: APIs that overload numbers and strings Phillips, Addison
• Re: APIs that overload numbers and strings Jonas Sicking
• Re: APIs that overload numbers and strings Allen Wirfs-Brock
• Re: Coordination Rick Waldron
• Re: Coordination (was: ES6 Modules) Kevin Smith
• Re: Coordination (was: ES6 Modules) Dirk Pranke
• Re: Coordination Brendan Eich
• Re: Coordination David Bruant
• Re: Coordination Arthur Barstow
• Re: Coordination Boris Zbarsky
• Re: APIs that overload numbers and strings Boris Zbarsky

Saturday, 13 April 2013

• Re: Coordination (was: ES6 Modules) Kevin Smith
• Re: APIs that overload numbers and strings Allen Wirfs-Brock
• Re: Coordination Rick Waldron
• Re: APIs that overload numbers and strings Tab Atkins Jr.
• Re: Coordination Tab Atkins Jr.
• APIs that overload numbers and strings Boris Zbarsky
• Re: Coordination Boris Zbarsky
• Re: Coordination (was: ES6 Modules) Dirk Pranke
• Re: Coordination (was: ES6 Modules) Anne van Kesteren
• Re: Coordination (was: ES6 Modules) Sam Tobin-Hochstadt
• Re: Coordination Brendan Eich
• Re: Coordination Anne van Kesteren
• Re: Coordination (was: ES6 Modules) Dirk Pranke
• Re: Outreach? (was Coordination/ES6 Modules) Dirk Pranke
• Re: Coordination Rick Waldron
• Re: Coordination Brendan Eich
• Re: Coordination Brendan Eich
• Re: Coordination Olli Pettay
• Re: Coordination Anne van Kesteren
• Re: Coordination David Bruant
• Re: Coordination Boris Zbarsky
• Re: Coordination (was: ES6 Modules) Rick Waldron
• Re: Outreach? (was Coordination/ES6 Modules) Rick Waldron
• Outreach? (was Coordination/ES6 Modules) Dirk Pranke
• Re: Coordination (was: ES6 Modules) Dirk Pranke

Friday, 12 April 2013

• [Bug 21670] Clarify that typeof InterfaceObject should be "function" bugzilla@jessica.w3.org
• Re: Coordination Allen Wirfs-Brock
• [Bug 21640] Dictionaries and callbacks should be distinguishable bugzilla@jessica.w3.org
• [Bug 21640] Dictionaries and callbacks should be distinguishable bugzilla@jessica.w3.org
• Re: Coordination (was: ES6 Modules) Mark S. Miller
• Re: Coordination Allen Wirfs-Brock
• Re: Coordination Charles McCathie Nevile
• Re: Coordination Anne van Kesteren
• Re: Coordination Boris Zbarsky
• Re: Coordination Rick Waldron
• Re: Coordination Boris Zbarsky
• Re: Coordination (was: ES6 Modules) Brian Kardell
• [Bug 21640] Dictionaries and callbacks should be distinguishable bugzilla@jessica.w3.org
• Re: Coordination Brendan Eich
• [Bug 21640] Dictionaries and callbacks should be distinguishable bugzilla@jessica.w3.org
• Re: Coordination (was: ES6 Modules) Anne van Kesteren
• Re: Coordination Boris Zbarsky
• Re: Coordination (was: ES6 Modules) Alex Russell
• [Bug 21640] Dictionaries and callbacks should be distinguishable bugzilla@jessica.w3.org
• Re: Coordination (was: ES6 Modules) Rick Waldron
• [Bug 21640] Dictionaries and callbacks should be distinguishable bugzilla@jessica.w3.org
• [Bug 21640] Dictionaries and callbacks should be distinguishable bugzilla@jessica.w3.org
• [Bug 21640] Dictionaries and callbacks should be distinguishable bugzilla@jessica.w3.org
• Re: Coordination (was: ES6 Modules) Alex Russell
• [Bug 21640] Dictionaries and callbacks should be distinguishable bugzilla@jessica.w3.org
• [Bug 21640] Dictionaries and callbacks should be distinguishable bugzilla@jessica.w3.org
• [Bug 21640] Dictionaries and callbacks should be distinguishable bugzilla@jessica.w3.org
• [Bug 21640] Dictionaries and callbacks should be distinguishable bugzilla@jessica.w3.org
• [Bug 21640] Dictionaries and callbacks should be distinguishable bugzilla@jessica.w3.org
• [Bug 21591] String constant on NavigatorID is invalid per WebIDL bugzilla@jessica.w3.org
• [Bug 21591] String constant on NavigatorID is invalid per WebIDL bugzilla@jessica.w3.org
• [Bug 21591] String constant on NavigatorID is invalid per WebIDL bugzilla@jessica.w3.org
• [Bug 21591] String constant on NavigatorID is invalid per WebIDL bugzilla@jessica.w3.org

Thursday, 11 April 2013

• [Bug 21591] String constant on NavigatorID is invalid per WebIDL bugzilla@jessica.w3.org
• [Bug 21670] Clarify that typeof InterfaceObject should be "function" bugzilla@jessica.w3.org
• [Bug 21670] Clarify that typeof InterfaceObject should be "function" bugzilla@jessica.w3.org
• [Bug 21669] Callable interface objects should be instance of Function bugzilla@jessica.w3.org
• [Bug 21589] SelectionMode enum should not have a trailing comma bugzilla@jessica.w3.org
• [Bug 21591] String constant on NavigatorID is invalid per WebIDL bugzilla@jessica.w3.org
• [Bug 21670] New: Clarify that typeof InterfaceObject should be "function" bugzilla@jessica.w3.org
• [Bug 21669] New: Callable interface objects should be instance of Function bugzilla@jessica.w3.org
• Re: [webcomponents]: Platonic form of custom elements declarative syntax Allen Wirfs-Brock
• Re: [webcomponents]: Platonic form of custom elements declarative syntax Boris Zbarsky
• Re: [webcomponents]: Platonic form of custom elements declarative syntax Boris Zbarsky
• Class side inheritance in WebIDL (was Re: [webcomponents]: Platonic form of custom elements declarative syntax) Erik Arvidsson
• Re: [webcomponents]: Platonic form of custom elements declarative syntax Allen Wirfs-Brock
• Re: [webcomponents]: Platonic form of custom elements declarative syntax Boris Zbarsky
• Coordination (was: ES6 Modules) Robin Berjon
• Re: Structured clones Anne van Kesteren

Wednesday, 10 April 2013

• Re: Structured clones Mark S. Miller
• Structured clones Anne van Kesteren

Tuesday, 9 April 2013

• Re: ES6 Modules Brendan Eich
• Re: ES6 Modules Anne van Kesteren
• Re: ES6 Modules Sam Tobin-Hochstadt
• [Bug 21640] New: Dictionaries and callbacks should be distinguishable bugzilla@jessica.w3.org
• Re: ES6 Modules Brendan Eich
• Re: ES6 Modules Anne van Kesteren

Monday, 8 April 2013

• Re: ES6 Modules Till Schneidereit
• Re: ES6 Modules Sam Tobin-Hochstadt
• Re: ES6 Modules Allen Wirfs-Brock
• Re: ES6 Modules Kevin Smith
• Re: ES6 Modules Rick Waldron
• Re: ES6 Modules Anne van Kesteren
• Re: ES6 Modules David Bruant
• Re: ES6 Modules Erik Arvidsson
• Re: ES6 Modules Anne van Kesteren
• Re: ES6 Modules Rick Waldron
• ES6 Modules Anne van Kesteren

Tuesday, 2 April 2013

• Re: Catching exceptions Allen Wirfs-Brock
• Re: Catching exceptions Rick Waldron
• Re: Catching exceptions Anne van Kesteren
• Re: Catching exceptions Rick Waldron
• Catching exceptions Anne van Kesteren

Monday, 1 April 2013

• [Bug 21492] Typo about preventExtensions bugzilla@jessica.w3.org
• [Bug 21492] New: Typo about preventExtensions bugzilla@jessica.w3.org

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