public-script-coord@w3.org from January to March 2013 by date

Thursday, 28 March 2013

[Bug 21422] New: Futures bugzilla@jessica.w3.org

Monday, 25 March 2013

Re: IDL: number types Boris Zbarsky
Re: IDL: number types Sam Tobin-Hochstadt
Re: IDL: number types Anne van Kesteren

Saturday, 23 March 2013

Re: IDL: number types Sam Tobin-Hochstadt

Monday, 25 March 2013

[Bug 21270] Introduce syntax for getters that keep returning the same object bugzilla@jessica.w3.org

Friday, 22 March 2013

Re: IDL: number types Alex Russell
Re: IDL: number types Rick Waldron
Re: IDL: number types Rick Waldron
Re: IDL: number types Boris Zbarsky
Re: IDL: number types Boris Zbarsky
Re: IDL: number types Boris Zbarsky
Re: IDL: number types Rick Waldron
Re: IDL: number types Allen Wirfs-Brock
[WebIDL] editorial: unrestricted double and precision Dirk Schulze

Thursday, 21 March 2013

Re: IDL: number types Boris Zbarsky
Re: IDL: number types Allen Wirfs-Brock

Wednesday, 20 March 2013

Re: IDL: number types Boris Zbarsky
Re: IDL: number types Boris Zbarsky
Re: IDL: number types Allen Wirfs-Brock
RE: IDL: number types Travis Leithead
Re: IDL: number types Allen Wirfs-Brock
Re: IDL: number types Boris Zbarsky
RE: IDL: number types Domenic Denicola
Re: IDL: number types Erik Arvidsson
Re: IDL: number types Boris Zbarsky
Re: IDL: number types Boris Zbarsky
RE: IDL: number types Domenic Denicola
Re: IDL: number types Boris Zbarsky
Re: IDL: number types Boris Zbarsky
Re: IDL: number types Boris Zbarsky
Re: IDL: number types Boris Zbarsky
Re: IDL: number types Boris Zbarsky
Re: IDL: number types Yehuda Katz
Re: IDL: number types Yehuda Katz
Re: IDL: number types Anne van Kesteren
RE: IDL: number types Domenic Denicola
Re: IDL: number types Anne van Kesteren
Re: IDL: number types Marcos Caceres
RE: IDL: number types Domenic Denicola
Re: IDL: number types Marcos Caceres
Re: IDL: number types Boris Zbarsky
Re: IDL: number types Marcos Caceres

Tuesday, 19 March 2013

Re: IDL: number types Dirk Schulze
Re: IDL: number types Boris Zbarsky
Re: IDL: number types Anne van Kesteren
Re: IDL: number types Boris Zbarsky
IDL: number types Anne van Kesteren

Friday, 15 March 2013

Re: Contextual auto-escaping corner cases Ian Hickson
Re: E4H compatible with string templates Mike Samuel
Re: Contextual auto-escaping corner cases Mike Samuel
Re: Contextual auto-escaping corner cases Tab Atkins Jr.
[Bug 21295] overload resolution: are DOMString and sequence<T> distinguishable now? bugzilla@jessica.w3.org
Re: E4H compatible with string templates Brendan Eich
Re: E4H compatible with string templates Bjoern Hoehrmann
Re: E4H compatible with string templates Tab Atkins Jr.
Re: E4H compatible with string templates Tab Atkins Jr.
Re: E4H compatible with string templates Mike Samuel
Re: E4H compatible with string templates Brendan Eich
Re: E4H compatible with string templates Tab Atkins Jr.
Re: E4H compatible with string templates Bjoern Hoehrmann
Re: E4H compatible with string templates Mike Samuel

Thursday, 14 March 2013

Re: E4H compatible with string templates Brendan Eich
[Bug 21295] New: overload resolution: are DOMString and sequence<T> distinguishable now? bugzilla@jessica.w3.org
Re: E4H compatible with string templates Tab Atkins Jr.
Re: E4H compatible with string templates Mike Samuel
Re: E4H compatible with string templates Ian Hickson
Contextual auto-escaping corner cases Mike Samuel
Re: E4H and constructing DOMs Mike Samuel
E4H compatible with string templates Mike Samuel

Wednesday, 13 March 2013

[Bug 21270] Introduce syntax for getters that keep returning the same object bugzilla@jessica.w3.org
[Bug 21270] Introduce syntax for getters that keep returning the same object bugzilla@jessica.w3.org
[Bug 21270] Introduce syntax for getters that keep returning the same object bugzilla@jessica.w3.org
[Bug 21270] New: Introduce syntax for getters that keep returning the same object bugzilla@jessica.w3.org
Re: E4H and constructing DOMs Tab Atkins Jr.
Re: E4H and constructing DOMs Mike Samuel

Tuesday, 12 March 2013

Re: E4H and constructing DOMs Ian Hickson
Re: E4H and constructing DOMs Mike Samuel
[Bug 17749] [WebIDL] Nit: "unrestricted double type" defined as 32-bit bugzilla@jessica.w3.org
[Bug 21251] Typos: unrestricted double describing 32-bit float (copy/paste error) bugzilla@jessica.w3.org
Re: E4H and constructing DOMs Ian Hickson
Re: E4H and constructing DOMs Mike Samuel
Re: E4H and constructing DOMs Bjoern Hoehrmann
Re: E4H and constructing DOMs Mike Samuel
Re: E4H and constructing DOMs Bjoern Hoehrmann
Re: E4H and constructing DOMs Bjoern Hoehrmann
Re: html template string handler WAS: E4H and constructing DOMs Mike Samuel
Re: E4H and constructing DOMs Mike Samuel

Monday, 11 March 2013

Re: E4H and constructing DOMs Ian Hickson
Re: html template string handler WAS: E4H and constructing DOMs Ian Hickson
Re: html template string handler WAS: E4H and constructing DOMs Mike Samuel
Re: E4H and constructing DOMs Mike Samuel
Re: html template string handler WAS: E4H and constructing DOMs Adam Barth
Re: html template string handler WAS: E4H and constructing DOMs Tab Atkins Jr.
Re: html template string handler WAS: E4H and constructing DOMs Adam Barth
Re: html template string handler WAS: E4H and constructing DOMs Anne van Kesteren
Re: E4H and constructing DOMs Ian Hickson
Re: E4H and constructing DOMs Mike Samuel
Re: html template string handler WAS: E4H and constructing DOMs Adam Barth
Re: html template string handler WAS: E4H and constructing DOMs Ian Hickson
Re: html template string handler WAS: E4H and constructing DOMs Allen Wirfs-Brock
[Bug 21251] Typos: unrestricted double describing 32-bit float (copy/paste error) bugzilla@jessica.w3.org
[Bug 21251] New: Typos: double/unrestricted double describing "float" (copy/paste error) bugzilla@jessica.w3.org
html template string handler WAS: E4H and constructing DOMs Ojan Vafai
Re: E4H and constructing DOMs Ian Hickson
Re: E4H and constructing DOMs Adam Barth
Re: E4H and constructing DOMs Boris Zbarsky
Re: E4H and constructing DOMs Jonas Sicking
Re: E4H and constructing DOMs Jonas Sicking

Sunday, 10 March 2013

Re: A design for Futures/Promises in DOM Alex Russell
Re: E4H and constructing DOMs Mike Samuel
Re: E4H and constructing DOMs Mike Samuel
Re: E4H and constructing DOMs Bjoern Hoehrmann
Re: Re: E4H and constructing DOMs Adam Barth
Re: Re: E4H and constructing DOMs Mark S. Miller
Re: E4H and constructing DOMs Ojan Vafai
Re: E4H and constructing DOMs Maciej Stachowiak
Re: E4H and constructing DOMs Brendan Eich
Re: E4H and constructing DOMs Allen Wirfs-Brock
Re: E4H and constructing DOMs Allen Wirfs-Brock
Re: E4H and constructing DOMs Maciej Stachowiak
Re: E4H and constructing DOMs Maciej Stachowiak
Re: E4H and constructing DOMs Brendan Eich
Re: E4H and constructing DOMs Allen Wirfs-Brock

Saturday, 9 March 2013

Re: E4H and constructing DOMs Brendan Eich
Re: E4H and constructing DOMs Adam Barth
Re: E4H and constructing DOMs Allen Wirfs-Brock
Re: E4H and constructing DOMs Garrett Smith
Re: E4H and constructing DOMs Ojan Vafai
Re: E4H and constructing DOMs Adam Barth
Re: E4H and constructing DOMs Brendan Eich
RE: E4H and constructing DOMs Domenic Denicola
Re: E4H and constructing DOMs Jonas Sicking
Re: E4H and constructing DOMs Mike Samuel
Re: E4H and constructing DOMs Bjoern Hoehrmann

Friday, 8 March 2013

Re: E4H and constructing DOMs Mike Samuel
Re: E4H and constructing DOMs Mike Samuel
Re: E4H and constructing DOMs Adam Barth
Re: E4H and constructing DOMs Allen Wirfs-Brock
Re: E4H and constructing DOMs Jonas Sicking
Re: E4H and constructing DOMs Adam Barth
Re: E4H and constructing DOMs Jonas Sicking
Re: E4H and constructing DOMs Mike Samuel
Re: E4H and constructing DOMs Maciej Stachowiak
Re: E4H and constructing DOMs Mark S. Miller
Re: E4H and constructing DOMs Mike Samuel
Re: E4H and constructing DOMs Maciej Stachowiak
Re: E4H and constructing DOMs Jonas Sicking
Re: E4H and constructing DOMs Mark S. Miller
Re: E4H and constructing DOMs Ian Hickson
Re: E4H and constructing DOMs Rick Waldron
Re: E4H and constructing DOMs Adam Barth
Re: E4H and constructing DOMs Mike Samuel
Re: E4H and constructing DOMs Mike Samuel
Re: Re: E4H and constructing DOMs Adam Barth
Re: Re: E4H and constructing DOMs Adam Barth
Re: Re: E4H and constructing DOMs Mike Samuel

Thursday, 7 March 2013

Re: E4H and constructing DOMs Adam Barth
Re: E4H and constructing DOMs Allen Wirfs-Brock
Re: E4H and constructing DOMs Adam Barth
Re: E4H and constructing DOMs Brendan Eich
Re: E4H and constructing DOMs Allen Wirfs-Brock
Re: E4H and constructing DOMs Ian Hickson
Re: E4H and constructing DOMs Allen Wirfs-Brock
Re: E4H and constructing DOMs Ian Hickson
Re: A design for Futures/Promises in DOM Mark S. Miller
A design for Futures/Promises in DOM Alex Russell
E4H and constructing DOMs Rick Waldron
Re: E4H and constructing DOMs Alex Russell
E4H and constructing DOMs Ojan Vafai

Monday, 4 March 2013

Why do we allow overloads on legacycallers? Boris Zbarsky

Friday, 1 March 2013

New ECMAScript Internationalization API Specification draft Norbert Lindenberg
Re: Standardizing console APIs: Where? Robin Berjon

Thursday, 28 February 2013

Re: Standardizing console APIs: Where? Boris Zbarsky
Re: Standardizing console APIs: Where? Jorge Chamorro
Re: Standardizing console APIs: Where? Robin Berjon
Re: Standardizing console APIs: Where? Michael[tm] Smith
Re: Standardizing console APIs: Where? Robin Berjon

Wednesday, 27 February 2013

Re: Standardizing console APIs: Where? Marcos Caceres
Re: Standardizing console APIs: Where? Boris Zbarsky
Re: Standardizing console APIs: Where? Thaddee Tyl
RE: Standardizing console APIs: Where? François REMY
Re: Standardizing console APIs: Where? Garrett Smith
Re: Standardizing console APIs: Where? Brian Kardell
RE: Standardizing console APIs: Where? François REMY
Re: Standardizing console APIs: Where? Thaddee Tyl
Re: Standardizing console APIs: Where? Robin Berjon
Re: Standardizing console APIs: Where? Alex Russell
Re: Standardizing console APIs: Where? Allen Wirfs-Brock
Re: Standardizing console APIs: Where? Mark S. Miller

Tuesday, 26 February 2013

Re: Standardizing console APIs: Where? Brian Kardell
Re: Standardizing console APIs: Where? Boris Zbarsky
Re: Standardizing console APIs: Where? Jorge Chamorro
Re: Standardizing console APIs: Where? Marcos Caceres
RE: Standardizing console APIs: Where? François REMY
Re: Standardizing console APIs: Where? Jorge Chamorro
RE: Standardizing console APIs: Where? Domenic Denicola

Monday, 25 February 2013

RE: Standardizing console APIs: Where? Travis Leithead
Re: Standardizing console APIs: Where? Brian Kardell
Re: Standardizing console APIs: Where? Marcos Caceres
Re: Standardizing console APIs: Where? Marcos Caceres
Re: Standardizing console APIs: Where? Brian Kardell
Re: Standardizing console APIs: Where? Clint Hill
Re: Standardizing console APIs: Where? Marcos Caceres
Re: Standardizing console APIs: Where? Robin Berjon
Re: Standardizing console APIs: Where? Clint Hill
Re: Standardizing console APIs: Where? Marcos Caceres
Re: Standardizing console APIs: Where? Brian Kardell
Re: Standardizing console APIs: Where? Robin Berjon
Re: Standardizing console APIs: Where? Marcos Caceres
Re: Standardizing console APIs: Where? Thaddee Tyl

Saturday, 23 February 2013

Re: Standardizing console APIs: Where? Charles McCathie Nevile
Re: Standardizing console APIs: Where? Garrett Smith

Friday, 22 February 2013

Re: Standardizing console APIs: Where? Rick Waldron
Standardizing console APIs: Where? Brian Kardell

Thursday, 21 February 2013

[Bug 21076] Remove _-escape mechanism for identifiers bugzilla@jessica.w3.org
[Bug 21076] New: Remove _-escape mechanism for identifiers bugzilla@jessica.w3.org
[Bug 21073] merge [Unforgeable] and readonly into unforgeable bugzilla@jessica.w3.org
[Bug 21073] merge [Unforgeable] and readonly into unforgeable bugzilla@jessica.w3.org
[Bug 21073] merge [Unforgeable] and readonly into unforgeable bugzilla@jessica.w3.org
[Bug 21073] merge [Unforgeable] and readonly into unforgeable bugzilla@jessica.w3.org
[Bug 21073] New: merge [Unforgeable] and readonly into unforgeable bugzilla@jessica.w3.org
[Bug 21069] [Unforgeable] attributes as data property bugzilla@jessica.w3.org
[Bug 21069] [Unforgeable] attributes as data property bugzilla@jessica.w3.org
[Bug 21069] [Unforgeable] attributes as data property bugzilla@jessica.w3.org
[Bug 21069] [Unforgeable] attributes as data property bugzilla@jessica.w3.org
[Bug 21069] [Unforgeable] attributes as data property bugzilla@jessica.w3.org
[Bug 21069] [Unforgeable] attributes as data property bugzilla@jessica.w3.org
[Bug 21069] [Unforgeable] attributes as data property bugzilla@jessica.w3.org
[Bug 21069] New: [Unforgeable] attributes as data property bugzilla@jessica.w3.org

Tuesday, 19 February 2013

[Bug 21048] Broken Links to ES6 Draft bugzilla@jessica.w3.org
[Bug 21048] New: Broken Links to ES6 Draft bugzilla@jessica.w3.org

Wednesday, 13 February 2013

Re: How to represent at key-value map in WebIDL Tab Atkins Jr.
Re: How to represent at key-value map in WebIDL Boris Zbarsky
How to represent at key-value map in WebIDL Adam Bergkvist

Tuesday, 12 February 2013

Re: [cssom] Proposal for obtaining robust style information via Javascript - getStyle() Garrett Smith

Monday, 11 February 2013

Checking for (JSON) serialisable object Marcos Caceres

Sunday, 10 February 2013

Re: [cssom] Proposal for obtaining robust style information via Javascript - getStyle() Cameron McCormack

Saturday, 9 February 2013

Re: [cssom] Proposal for obtaining robust style information via Javascript - getStyle() Tab Atkins Jr.
RE: [cssom] Proposal for obtaining robust style information via Javascript - getStyle() François REMY
Re: [cssom] Proposal for obtaining robust style information via Javascript - getStyle() Tab Atkins Jr.
Re: [cssom] Proposal for obtaining robust style information via Javascript - getStyle() Garrett Smith

Friday, 8 February 2013

Re: [cssom] Proposal for obtaining robust style information via Javascript - getStyle() Cameron McCormack

Thursday, 7 February 2013

Re: [cssom] Proposal for obtaining robust style information via Javascript - getStyle() Bjoern Hoehrmann
Re: [cssom] Proposal for obtaining robust style information via Javascript - getStyle() Anne van Kesteren

Wednesday, 6 February 2013

Re: [cssom] Proposal for obtaining robust style information via Javascript - getStyle() Bjoern Hoehrmann

Friday, 1 February 2013

Re: Fwd: [IndexedDB] Event handlers Garrett Smith
Re: Fwd: [IndexedDB] Event handlers David Bruant
RE: Interaction between WebIDL operations and ES6 proxies François REMY
Re: Interaction between WebIDL operations and ES6 proxies David Bruant
Re: Interaction between WebIDL operations and ES6 proxies Anne van Kesteren
Re: Interaction between WebIDL operations and ES6 proxies Anne van Kesteren
Re: Interaction between WebIDL operations and ES6 proxies David Bruant
Re: Interaction between WebIDL operations and ES6 proxies Rick Waldron
Re: Fwd: [IndexedDB] Event handlers Cameron McCormack
[Bug 20836] What happens when a dictionary references itself? bugzilla@jessica.w3.org

Thursday, 31 January 2013

[Bug 20836] What happens when a dictionary references itself? bugzilla@jessica.w3.org
[Bug 20836] What happens when a dictionary references itself? bugzilla@jessica.w3.org
[Bug 20836] What happens when a dictionary references itself? bugzilla@jessica.w3.org
[Bug 20836] What happens when a dictionary references itself? bugzilla@jessica.w3.org
[Bug 20836] What happens when a dictionary references itself? bugzilla@jessica.w3.org
Interaction between WebIDL operations and ES6 proxies David Bruant
Re: Fwd: [IndexedDB] Event handlers David Bruant
[Bug 20836] New: What happens when a dictionary references itself? bugzilla@jessica.w3.org

Friday, 25 January 2013

[Bug 20567] Change [[Prototype]] for concept-node-adopt? bugzilla@jessica.w3.org
[Bug 20567] Change [[Prototype]] for concept-node-adopt? bugzilla@jessica.w3.org
[Bug 20567] Change [[Prototype]] for concept-node-adopt? bugzilla@jessica.w3.org
[Bug 20567] Change [[Prototype]] for concept-node-adopt? bugzilla@jessica.w3.org
[Bug 20567] Change [[Prototype]] for concept-node-adopt? 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 20777] Getting a property from the global scope polluter ends up in an infinite loop bugzilla@jessica.w3.org
[Bug 20777] New: Getting a property from the global scope polluter ends up in an infinite loop bugzilla@jessica.w3.org
[Bug 20567] Change [[Prototype]] for concept-node-adopt? bugzilla@jessica.w3.org
[Bug 20567] Change [[Prototype]] for concept-node-adopt? bugzilla@jessica.w3.org
[Bug 20567] Change [[Prototype]] for concept-node-adopt? bugzilla@jessica.w3.org
[Bug 20567] Change [[Prototype]] for concept-node-adopt? bugzilla@jessica.w3.org
[Bug 20567] Change [[Prototype]] for concept-node-adopt? bugzilla@jessica.w3.org

Thursday, 24 January 2013

[Bug 20567] Change [[Prototype]] for concept-node-adopt? bugzilla@jessica.w3.org
[Bug 20567] Change [[Prototype]] for concept-node-adopt? bugzilla@jessica.w3.org
[Bug 20567] Change [[Prototype]] for concept-node-adopt? bugzilla@jessica.w3.org
[Bug 20567] Change [[Prototype]] for concept-node-adopt? bugzilla@jessica.w3.org
RE: Fwd: [IndexedDB] Event handlers Travis Leithead
[Bug 20737] "Call the [[DefineOwnProperty]] internal method ..." bugzilla@jessica.w3.org
[Bug 20735] n not defined in sequence algorithm bugzilla@jessica.w3.org
Re: Fwd: [IndexedDB] Event handlers Anne van Kesteren
Re: Solving the "how do I tell whether I have an HTML element?" (or image element, or whatever) problem Tom Van Cutsem
Re: Solving the "how do I tell whether I have an HTML element?" (or image element, or whatever) problem Cameron McCormack
[Bug 20567] Change [[Prototype]] for concept-node-adopt? bugzilla@jessica.w3.org
[Bug 20441] algorithms not marked as such bugzilla@jessica.w3.org
Re: Fwd: [IndexedDB] Event handlers Cameron McCormack
[Bug 20567] Change [[Prototype]] for concept-node-adopt? bugzilla@jessica.w3.org
[Bug 20735] n not defined in sequence algorithm bugzilla@jessica.w3.org
[Bug 20737] "Call the [[DefineOwnProperty]] internal method ..." bugzilla@jessica.w3.org

Wednesday, 23 January 2013

[Bug 20567] Change [[Prototype]] for concept-node-adopt? bugzilla@jessica.w3.org
[Bug 17648] [Awaiting ES6] Add iterators bugzilla@jessica.w3.org

Tuesday, 22 January 2013

[Bug 20737] "Call the [[DefineOwnProperty]] internal method ..." bugzilla@jessica.w3.org
[Bug 20737] "Call the [[DefineOwnProperty]] internal method ..." bugzilla@jessica.w3.org
[Bug 20737] "Call the [[DefineOwnProperty]] internal method ..." bugzilla@jessica.w3.org
[Bug 20737] New: "Call the [[DefineOwnProperty]] internal method ..." bugzilla@jessica.w3.org
[Bug 20731] Sequence algorithm seems incorrect bugzilla@jessica.w3.org
[Bug 20731] Sequence algorithm seems incorrect bugzilla@jessica.w3.org
[Bug 20735] n not defined in sequence algorithm bugzilla@jessica.w3.org
[Bug 20731] Sequence algorithm seems incorrect bugzilla@jessica.w3.org
[Bug 20735] n not defined in sequence algorithm bugzilla@jessica.w3.org
[Bug 20731] Sequence algorithm seems incorrect bugzilla@jessica.w3.org
[Bug 20731] Sequence algorithm seems incorrect bugzilla@jessica.w3.org
[Bug 20735] New: n not defined in sequence algorithm bugzilla@jessica.w3.org
[Bug 20731] Sequence algorithm seems incorrect bugzilla@jessica.w3.org
[Bug 20731] Sequence algorithm seems incorrect bugzilla@jessica.w3.org
[Bug 20731] Sequence algorithm seems incorrect bugzilla@jessica.w3.org
[Bug 20731] Sequence algorithm seems incorrect bugzilla@jessica.w3.org
[Bug 20731] Sequence algorithm seems incorrect bugzilla@jessica.w3.org
[Bug 16833] consider always exposing a "length" property for objects with indexed properties bugzilla@jessica.w3.org
[Bug 20441] algorithms not marked as such bugzilla@jessica.w3.org
[Bug 20731] New: Sequence algorithm seems incorrect bugzilla@jessica.w3.org
[Bug 20567] Change [[Prototype]] for concept-node-adopt? bugzilla@jessica.w3.org

Monday, 21 January 2013

Fwd: [IndexedDB] Event handlers David Bruant

Friday, 18 January 2013

Web IDL exceptions Anne van Kesteren

Thursday, 17 January 2013

Wednesday, 16 January 2013

Monday, 14 January 2013

[Bug 20560] misplaced comma bugzilla@jessica.w3.org
[Bug 20560] misplaced comma bugzilla@jessica.w3.org

Sunday, 13 January 2013

[Bug 20559] Typo in sequence conversion algo bugzilla@jessica.w3.org

Saturday, 12 January 2013

Re: [webidl.js] Implement the any type Cameron McCormack
[Bug 20653] Function object doesn't specify needing a "prototype" property bugzilla@jessica.w3.org
[Bug 20653] Function object doesn't specify needing a "prototype" property bugzilla@jessica.w3.org
[Bug 20653] Function object doesn't specify needing a "prototype" property bugzilla@jessica.w3.org
[Bug 20653] Function object doesn't specify needing a "prototype" property bugzilla@jessica.w3.org
[Bug 20653] Function object doesn't specify needing a "prototype" property bugzilla@jessica.w3.org
[Bug 20653] Function object doesn't specify needing a "prototype" property bugzilla@jessica.w3.org
[Bug 20653] New: Function object doesn't specify needing a "prototype" property bugzilla@jessica.w3.org

Thursday, 10 January 2013

RE: [webidl.js] Implement the any type François REMY
Re: [webidl.js] Implement the any type Anne van Kesteren
[webidl.js] Implement the any type François REMY

Tuesday, 8 January 2013

Monday, 7 January 2013

[Bug 20225] don't allow overridden operations and attribute getters/setters to be invoked on descendant objects bugzilla@jessica.w3.org
Re: [whatwg] Need to define same-origin policy for WebIDL operations/getters/setters Ian Hickson
Re: [whatwg] Need to define same-origin policy for WebIDL operations/getters/setters Cameron McCormack
[Bug 20158] Unrestricted typed dictionary bugzilla@jessica.w3.org

Saturday, 5 January 2013

[Bug 20158] Unrestricted typed dictionary bugzilla@jessica.w3.org
[Bug 20535] consider removing indexed property setters, creators and deleters bugzilla@jessica.w3.org
[Bug 20158] Unrestricted typed dictionary bugzilla@jessica.w3.org

Friday, 4 January 2013

[Bug 20158] Unrestricted typed dictionary bugzilla@jessica.w3.org
[Bug 20561] Objects supporting indexed properties bugzilla@jessica.w3.org
[Bug 20561] Objects supporting indexed properties bugzilla@jessica.w3.org
[Bug 20562] Objects supporting indexed properties bugzilla@jessica.w3.org
[Bug 20562] New: Objects supporting indexed properties bugzilla@jessica.w3.org
[Bug 20561] New: Objects supporting indexed properties bugzilla@jessica.w3.org
[Bug 20560] New: misplaced comma bugzilla@jessica.w3.org
[Bug 20559] New: Typo in sequence conversion algo bugzilla@jessica.w3.org

Thursday, 3 January 2013

[Bug 20535] consider removing indexed property setters, creators and deleters bugzilla@jessica.w3.org

Tuesday, 1 January 2013

Last message date: Thursday, 28 March 2013 16:08:24 UTC