www-dom@w3.org from April to June 2013 by date

Saturday, 29 June 2013

• [Bug 22515] Consider moving getElementBy* to ParentNode bugzilla@jessica.w3.org
• [Bug 22515] New: Consider moving getElementBy* to ParentNode bugzilla@jessica.w3.org

Friday, 28 June 2013

• [Bug 22514] New: "optionally with a document ownerDocument" bugzilla@jessica.w3.org
• [Bug 22513] New: "Run any cloning steps defined for node in other..." bugzilla@jessica.w3.org
• [Bug 22512] New: "Copy the following, depending on the type of node" bugzilla@jessica.w3.org
• RE: [promises] resolver's resolved flag check on promise callback Domenic Denicola
• Re: [promises] resolver's resolved flag check on promise callback Yutaka Hirano
• Re: [promises] resolver's resolved flag check on promise callback Anne van Kesteren
• [promises] resolver's resolved flag check on promise callback Yutaka Hirano

Thursday, 27 June 2013

• [promises] resolver's resolved flag check on promise callback Yutaka Hirano
• [Bug 22496] New: "A host-including inclusive ancestor is either a..." bugzilla@jessica.w3.org

Friday, 21 June 2013

• [Bug 21066] Provide an event path API bugzilla@jessica.w3.org

Thursday, 20 June 2013

• [Bug 21066] Provide an event path API bugzilla@jessica.w3.org
• Re: [promises] Difficulties with using constructors and promises together François REMY
• Re: [promises] Difficulties with using constructors and promises together Tab Atkins Jr.
• Re: [promises] Difficulties with using constructors and promises together Boris Zbarsky
• Re: [promises] Difficulties with using constructors and promises together Brandon Wallace
• Re: [promises] Difficulties with using constructors and promises together Dimitri Glazkov
• RE: [promises] Difficulties with using constructors and promises together Domenic Denicola
• Re: [promises] Difficulties with using constructors and promises together Boris Zbarsky
• [Bug 22153] DOMError name bugzilla@jessica.w3.org
• Re: [promises] Difficulties with using constructors and promises together Anne van Kesteren
• [Bug 22410] Attr.value = 'foo' doesn't seem to create a mutation record, according to spec bugzilla@jessica.w3.org

Wednesday, 19 June 2013

• [Bug 22410] New: Attr.value = 'foo' doesn't seem to create a mutation record, according to spec bugzilla@jessica.w3.org
• [promises] Difficulties with using constructors and promises together Tab Atkins Jr.
• [Bug 14072] Screen.alphaDepth missing bugzilla@jessica.w3.org
• [Bug 22321] Spec for DOMTokenList.toggle is very confusing bugzilla@jessica.w3.org
• Re: Deprecating Future's .then() Sean Hogan
• [D3E] June 18th Telco Notes Travis Leithead

Tuesday, 18 June 2013

• Re: DOM L3 Events Upcoming Telco: call for agenda topics Wez

Wednesday, 19 June 2013

• [Bug 22072] "current click count" deserves its own attribute bugzilla@jessica.w3.org

Tuesday, 18 June 2013

• Re: DOM L3 Events Upcoming Telco: call for agenda topics Кошмарчик
• Re: DOM L3 Events Upcoming Telco: call for agenda topics Arthur Barstow
• Re: [ui-events] MouseEvent details Simon Pieters
• [Bug 14071] Screen.{color,pixel}Depth not sufficiently distinguished bugzilla@jessica.w3.org
• [Bug 14072] Screen.alphaDepth missing bugzilla@jessica.w3.org
• [Bug 14072] Screen.alphaDepth missing bugzilla@jessica.w3.org
• [Bug 14071] Screen.{color,pixel}Depth not sufficiently distinguished bugzilla@jessica.w3.org
• [Bug 14071] Screen.{color,pixel}Depth not sufficiently distinguished bugzilla@jessica.w3.org
• [Bug 14072] Screen.alphaDepth missing bugzilla@jessica.w3.org
• [Bug 14072] Screen.alphaDepth missing bugzilla@jessica.w3.org
• [Bug 10533] Spec the non-visual aspects of scrollIntoView() as removed from HTML bugzilla@jessica.w3.org

Monday, 17 June 2013

• Re: Exceptions in event listeners triggered by dispatchEvent(). Glenn Maynard
• Re: Exceptions in event listeners triggered by dispatchEvent(). Bjoern Hoehrmann
• Re: Exceptions in event listeners triggered by dispatchEvent(). John Barton
• Re: Exceptions in event listeners triggered by dispatchEvent(). Ian Hickson
• DOM L3 Events Upcoming Telco: call for agenda topics Travis Leithead
• Re: Deprecating Future's .then() Mark S. Miller
• Re: [DOM Futures] Is there a typo in future wrapper callback? Sean Hogan
• Re: Deprecating Future's .then() Sean Hogan

Thursday, 13 June 2013

• [Bug 22357] New: Don't special case callable 'then' bugzilla@jessica.w3.org

Tuesday, 11 June 2013

• [Bug 14207] ElementCSSInlineStyle needs binding to Element bugzilla@jessica.w3.org

Monday, 10 June 2013

• [Bug 22321] New: Spec for DOMTokenList.toggle is very confusing bugzilla@jessica.w3.org

Saturday, 8 June 2013

• Re: Exceptions in event listeners triggered by dispatchEvent(). Jonas Sicking
• Re: Exceptions in event listeners triggered by dispatchEvent(). Simon Pieters
• 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: Exceptions in event listeners triggered by dispatchEvent(). Glenn Maynard
• Re: Exceptions in event listeners triggered by dispatchEvent(). Glenn Maynard
• Re: Exceptions in event listeners triggered by dispatchEvent(). Simon Pieters
• Re: [Futures] accept/resolve/reject on a resolver don't have clearly defined behavior if no value is passed Brendan Eich

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: [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: [Futures] Possible to multiply-resolve a resolver in weird ways Boris Zbarsky
• Re: [Futures] Possible to multiply-resolve a resolver in weird ways Sean Hogan
• Re: [Futures] Use of "context object" in the spec is really confusing Anne van Kesteren
• Re: [Futures] accept/resolve/reject on a resolver don't have clearly defined behavior if no value is passed Anne van Kesteren
• Re: [futures] Handling of exceptions in the "future wrapper callback" algorithm does not make it clear that they are in fact being caught Anne van Kesteren
• Re: [Futures] Possible to multiply-resolve a resolver in weird ways Anne van Kesteren
• Re: Deprecating Future's .then() Mark S. Miller
• Re: [Futures] Possible to multiply-resolve a resolver in weird ways Sean Hogan
• 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: [Futures] Possible to multiply-resolve a resolver in weird ways Boris Zbarsky
• Re: [Futures] Possible to multiply-resolve a resolver in weird ways Anne van Kesteren
• Re: Deprecating Future's .then() Mark S. Miller
• Re: Deprecating Future's .then() Sean Hogan
• Re: Deprecating Future's .then() Anne van Kesteren
• Re: Exceptions in event listeners triggered by dispatchEvent(). Glenn Maynard
• [Bug 22283] EventHandler and related infrastructure bugzilla@jessica.w3.org
• Re: Deprecating Future's .then() Mark S. Miller
• Re: Exceptions in event listeners triggered by dispatchEvent(). Anne van Kesteren
• Re: Exceptions in event listeners triggered by dispatchEvent(). John Barton
• [Bug 22283] New: EventHandler and related infrastructure bugzilla@jessica.w3.org
• Re: Exceptions in event listeners triggered by dispatchEvent(). Anne van Kesteren
• Re: Exceptions in event listeners triggered by dispatchEvent(). Simon Pieters
• Re: Deprecating Future's .then() Anne van Kesteren
• Re: Deprecating Future's .then() Anne van Kesteren
• Re: Deprecating Future's .then() Alex Russell
• Re: Exceptions in event listeners triggered by dispatchEvent(). Glenn Maynard
• [D3E] June 4, 2013 minutes recorded Travis Leithead

Tuesday, 4 June 2013

• Re: Exceptions in event listeners triggered by dispatchEvent(). John Barton
• Re: Exceptions in event listeners triggered by dispatchEvent(). Bjoern Hoehrmann
• Re: Exceptions in event listeners triggered by dispatchEvent(). Boris Zbarsky
• Re: Exceptions in event listeners triggered by dispatchEvent(). Bjoern Hoehrmann
• RE: Exceptions in event listeners triggered by dispatchEvent(). Domenic Denicola
• Re: Exceptions in event listeners triggered by dispatchEvent(). Boris Zbarsky
• RE: DOM L3 Events- Call for Agenda Topics! Travis Leithead
• Re: Deprecating Future's .then() Mark S. Miller
• Re: Deprecating Future's .then() Mark S. Miller
• RE: Exceptions in event listeners triggered by dispatchEvent(). Domenic Denicola
• RE: Deprecating Future's .then() Domenic Denicola
• Re: Deprecating Future's .then() Sam Tobin-Hochstadt
• Re: Deprecating Future's .then() Anne van Kesteren
• Re: Exceptions in event listeners triggered by dispatchEvent(). Glenn Maynard
• Re: Exceptions in event listeners triggered by dispatchEvent(). Boris Zbarsky
• Re: DOM L3 Events- Call for Agenda Topics! 河内 隆仁
• Re: DOM L3 Events- Call for Agenda Topics! 河内 隆仁
• Re: Deprecating Future's .then() Sam Tobin-Hochstadt
• Re: Exceptions in event listeners triggered by dispatchEvent(). John Barton

Monday, 3 June 2013

• Re: Exceptions in event listeners triggered by dispatchEvent(). John Barton

Tuesday, 4 June 2013

• Re: Exceptions in event listeners triggered by dispatchEvent(). John Barton
• Re: Exceptions in event listeners triggered by dispatchEvent(). Glenn Maynard
• Re: Exceptions in event listeners triggered by dispatchEvent(). Glenn Maynard

Monday, 3 June 2013

• Re: DOM L3 Events- Call for Agenda Topics! Arthur Barstow
• Re: Exceptions in event listeners triggered by dispatchEvent(). Glenn Maynard
• Re: Deprecating Future's .then() Mark S. Miller
• Re: Deprecating Future's .then() Tab Atkins Jr.
• Re: DOM L3 Events- Call for Agenda Topics! Кошмарчик
• DOM L3 Events- Call for Agenda Topics! Travis Leithead
• Re: Exceptions in event listeners triggered by dispatchEvent(). Jonas Sicking
• Re: Exceptions in event listeners triggered by dispatchEvent(). Anne van Kesteren
• Re: Exceptions in event listeners triggered by dispatchEvent(). Anne van Kesteren
• Re: Exceptions in event listeners triggered by dispatchEvent(). Glenn Maynard
• 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: Exceptions in event listeners triggered by dispatchEvent(). Anne van Kesteren
• Re: Deprecating Future's .then() Anne van Kesteren

Sunday, 2 June 2013

• Re: Deprecating Future's .then() Sean Hogan
• Re: Exceptions in event listeners triggered by dispatchEvent(). Glenn Maynard

Friday, 31 May 2013

• Exceptions in event listeners triggered by dispatchEvent(). johnjbarton
• [Futures] Possible to multiply-resolve a resolver in weird ways Boris Zbarsky
• [Futures] accept/resolve/reject on a resolver don't have clearly defined behavior if no value is passed Boris Zbarsky
• [Futures] Use of "context object" in the spec is really confusing Boris Zbarsky

Thursday, 30 May 2013

• [futures] Handling of exceptions in the "future wrapper callback" algorithm does not make it clear that they are in fact being caught Boris Zbarsky

Tuesday, 28 May 2013

• [Bug 15181] Override of non-recognised media type appears unsupported in xml-stylesheet processing bugzilla@jessica.w3.org

Thursday, 23 May 2013

• [Bug 22153] New: DOMError name bugzilla@jessica.w3.org

Wednesday, 22 May 2013

• Re: [DOM Events] Call for Agenda Topics: D3E Telco tomorrow (May 21st, 2013 PST) 河内 隆仁
• Re: [DOM Events] Call for Agenda Topics: D3E Telco tomorrow (May 21st, 2013 PST) 河内 隆仁

Tuesday, 21 May 2013

• Re: [DOM Events] Call for Agenda Topics: D3E Telco tomorrow (May 21st, 2013 PST) Wez
• RE: [DOM Events] Call for Agenda Topics: D3E Telco tomorrow (May 21st, 2013 PST) Travis Leithead
• Re: [DOM Events] Call for Agenda Topics: D3E Telco tomorrow (May 21st, 2013 PST) Кошмарчик
• RE: [DOM Events] Call for Agenda Topics: D3E Telco tomorrow (May 21st, 2013 PST) Travis Leithead

Monday, 20 May 2013

• Re: Deprecating Future's .then() Sean Hogan
• [DOM Events] Call for Agenda Topics: D3E Telco tomorrow (May 21st, 2013 PST) Travis Leithead
• Re: Deprecating Future's .then() Tab Atkins Jr.
• Re: Review of use of Future spec terminology Marcos Caceres
• Re: Deprecating Future's .then() Sean Hogan
• Re: Deprecating Future's .then() Tab Atkins Jr.
• Re: Deprecating Future's .then() Sean Hogan

Sunday, 19 May 2013

• Re: Deprecating Future's .then() Tab Atkins Jr.

Saturday, 18 May 2013

• Deprecating Future's .then() Sean Hogan
• [Bug 22084] New: Consistent key names in D3E spec bugzilla@jessica.w3.org
• [Bug 22083] New: Break D3E Key Value table into smaller chunks of related keys bugzilla@jessica.w3.org
• [Bug 22082] New: Review and cleanup examples in D3E spec bugzilla@jessica.w3.org
• [Bug 21834] Dead keys--should they just use the composition event model? bugzilla@jessica.w3.org
• Re: [DOM3 Events] space key should be always "Spacebar" for KeyboardEvent.key? Masayuki Nakano
• [Bug 22081] New: Needs to be clear whether "Spacebar" key value should be used when non-ASCII space (U+20) is inputted bugzilla@jessica.w3.org

Friday, 17 May 2013

• [Bug 22073] New: 'Meta' key is the same as the 'OS' or 'Win' key bugzilla@jessica.w3.org
• [Bug 22072] New: "current click count" deserves its own attribute bugzilla@jessica.w3.org
• [Bug 22071] New: Remove 'char' from KeyboardEvent in DOM3 bugzilla@jessica.w3.org
• [Bug 22070] New: Revive textInput in DOM3 bugzilla@jessica.w3.org
• [Bug 22069] New: Names for media keys should be organized bugzilla@jessica.w3.org
• [Bug 22068] New: Remove Appendix A and replace with references to UI Events spec bugzilla@jessica.w3.org
• [Bug 17625] Shouldn't ExSel key value be Exsel? bugzilla@jessica.w3.org

Wednesday, 15 May 2013

• [Bug 22051] New: DOMTokenList clarifications bugzilla@jessica.w3.org
• Review of use of Future spec terminology Marcos Caceres
• [DOM Futures] Is there a typo in future wrapper callback? Sean Hogan
• [DOM Futures] Is there a typo in future wrapper callback? Sean Hogan

Tuesday, 14 May 2013

• Re: Re: [D4E] KeyboardEvent.code and KeyboardEvent.queryKeyCap() are very strange spec Hallvord Reiar Michaelsen Steen
• [Bug 14197] Inconsistent naming convention - media_query_list bugzilla@jessica.w3.org
• [Bug 11329] Browsers must generate resize event during a zoom. bugzilla@jessica.w3.org

Thursday, 9 May 2013

• Re: [DOM3 Events] space key should be always "Spacebar" for KeyboardEvent.key? Masayuki Nakano
• Re: [DOM3 Events] space key should be always "Spacebar" for KeyboardEvent.key? Wez
• Re: [DOM3 Events] space key should be always "Spacebar" for KeyboardEvent.key? Hallvord R. M. Steen
• Re: [DOM3 Events] space key should be always "Spacebar" for KeyboardEvent.key? Wez
• [Bug 21986] New: Element.attributes needs to have a named getter bugzilla@jessica.w3.org
• Re: [Future] reject() value type Mounir Lamouri
• [Bug 21981] New: Key name definition about "foo[0-9]+" bugzilla@jessica.w3.org
• [DOM3 Events] space key should be always "Spacebar" for KeyboardEvent.key? Masayuki Nakano

Wednesday, 8 May 2013

• Re: [Future] First arguments should not be optional Boris Zbarsky
• Re: [Future] First arguments should not be optional Cameron McCormack
• Re: [Future] First arguments should not be optional Garrett Smith
• [Bug 21976] New: [imports]: Preventing DOM hierarchy cycles bugzilla@jessica.w3.org
• RE: [Future] First arguments should not be optional Domenic Denicola
• Re: [Future] First arguments should not be optional Jonas Sicking
• Re: [Future] First arguments should not be optional Jonas Sicking
• Re: [Future] First arguments should not be optional Boris Zbarsky
• Re: [Future] reject() value type David Bruant
• RE: [Future] First arguments should not be optional Domenic Denicola
• RE: [Future] reject() value type Domenic Denicola
• Re: [Future] reject() value type Anne van Kesteren
• [Future] reject() value type Mounir Lamouri
• [Future] First arguments should not be optional Mounir Lamouri
• [Bug 11328] Canvas authors needs to be able to assess pixel resolution to rescale canvas elements bugzilla@jessica.w3.org
• [Bug 21966] New: D3E spec should prohibit browser vendors name original key name bugzilla@jessica.w3.org
• [D3E] Draft minutes from 7-May-2013 call [Was: Re: WebApps DOM3 Events Wiki page] Arthur Barstow

Tuesday, 7 May 2013

• Re: Proposal for a DOM L3 Events Telecon Arthur Barstow
• RE: Proposal for a DOM L3 Events Telecon Travis Leithead
• Re: Proposal for a DOM L3 Events Telecon Charles McCathie Nevile
• Re: Proposal for a DOM L3 Events Telecon Кошмарчик
• Re: [D4E] KeyboardEvent.code and KeyboardEvent.queryKeyCap() are very strange spec Masayuki Nakano
• Re: [D4E] KeyboardEvent.code and KeyboardEvent.queryKeyCap() are very strange spec Masayuki Nakano
• Re: Proposal for a DOM L3 Events Telecon Masayuki Nakano

Wednesday, 1 May 2013

• Re: Proposal for a DOM L3 Events Telecon 河内 隆仁
• RE: Proposal for a DOM L3 Events Telecon Travis Leithead
• Re: Proposal for a DOM L3 Events Telecon Wez

Tuesday, 30 April 2013

• Re: Proposal for a DOM L3 Events Telecon Кошмарчик
• [D3E] Gecko will start supporting KeyboardEvent.key from Firefox 23, but only for non-printable keys Masayuki Nakano

Monday, 29 April 2013

• [Bug 17201] HTMLCollection.prototype.namedItem behavior not defined for HTMLPropertiesCollection bugzilla@jessica.w3.org
• Re: Proposal for a DOM L3 Events Telecon Кошмарчик
• Proposal for a DOM L3 Events Telecon Travis Leithead

Friday, 26 April 2013

• [Bug 21853] New: Allow subclasses of futures to decide what then/catch create bugzilla@jessica.w3.org
• Re: hasFeature revisited Anne van Kesteren
• Re: hasFeature revisited Dirk Schulze

Thursday, 25 April 2013

• [Bug 21834] New: Dead keys--should they just use the composition event model? bugzilla@jessica.w3.org
• [Bug 21830] New: KeyboardEvent.locale is too general. bugzilla@jessica.w3.org

Wednesday, 24 April 2013

• Re: Resolving Futures w/multiple values Dave Longley
• Re: Resolving Futures w/multiple values Brandon Wallace
• Re: Resolving Futures w/multiple values Dave Longley
• Re: Resolving Futures w/multiple values Dave Longley
• Re: Resolving Futures w/multiple values Bjoern Hoehrmann
• Re: [futures] Add convenience functions for immediate/canceled promises Bjoern Hoehrmann
• Re: [futures] Add convenience functions for immediate/canceled promises Anne van Kesteren

Tuesday, 23 April 2013

• RE: Resolving Futures w/multiple values Domenic Denicola
• Re: Resolving Futures w/multiple values Tab Atkins Jr.
• Re: Resolving Futures w/multiple values Dave Longley
• Re: Resolving Futures w/multiple values Brandon Wallace
• RE: Resolving Futures w/multiple values Domenic Denicola
• Re: Resolving Futures w/multiple values Tab Atkins Jr.
• Resolving Futures w/multiple values Dave Longley

Friday, 19 April 2013

• Re: [futures] Making ProgressFuture immediate Tab Atkins Jr.
• Re: [futures] Folding .progress() into .then() for ProgressFuture Mounir Lamouri
• Re: [futures] Making ProgressFuture immediate Mounir Lamouri

Thursday, 18 April 2013

• Re: [futures] Folding .progress() into .then() for ProgressFuture Tab Atkins Jr.
• Re: [futures] Making ProgressFuture immediate Tab Atkins Jr.
• Re: [futures] Add convenience functions for immediate/canceled promises Tab Atkins Jr.
• Re: [futures] Add convenience functions for immediate/canceled promises Anne van Kesteren
• Re: [futures] Making ProgressFuture immediate Mounir Lamouri
• Re: [futures] Folding .progress() into .then() for ProgressFuture Mounir Lamouri
• Re: [futures] Add convenience functions for immediate/canceled promises Mounir Lamouri
• [Bug 21740] New: Guidance on DOMError and futures bugzilla@jessica.w3.org
• Re: DOM HTML specification - DOM levels 3 and 4 Anne van Kesteren

Wednesday, 17 April 2013

• DOM HTML specification - DOM levels 3 and 4 Thomas Fétiveau

Tuesday, 16 April 2013

• Re: Seeking guidance on MIDIMessageEvent design, was Fw: [MIDI] bump: Issue 1: MIDIEvent lacking constructor Chris Wilson
• Re: Seeking guidance on MIDIMessageEvent design, was Fw: [MIDI] bump: Issue 1: MIDIEvent lacking constructor Anne van Kesteren
• Re: Seeking guidance on MIDIMessageEvent design, was Fw: [MIDI] bump: Issue 1: MIDIEvent lacking constructor Chris Wilson
• Re: [futures] Folding .progress() into .then() for ProgressFuture Anne van Kesteren

Monday, 15 April 2013

• Re: [futures] Persistent/Repeated Future that doesn't resolve Jonas Sicking
• Re: Seeking guidance on MIDIMessageEvent design, was Fw: [MIDI] bump: Issue 1: MIDIEvent lacking constructor Marcos Caceres
• Re: hasFeature revisited Simon Pieters
• Fwd: hasFeature revisited Anne van Kesteren
• Re: hasFeature revisited Boris Zbarsky
• Re: hasFeature revisited Anne van Kesteren
• Re: hasFeature revisited Simon Pieters
• hasFeature revisited Anne van Kesteren
• Re: [futures] Persistent/Repeated Future that doesn't resolve Anne van Kesteren
• Re: Seeking guidance on MIDIMessageEvent design, was Fw: [MIDI] bump: Issue 1: MIDIEvent lacking constructor Ms2ger

Sunday, 14 April 2013

• Seeking guidance on MIDIMessageEvent design, was Fw: [MIDI] bump: Issue 1: MIDIEvent lacking constructor Marcos Caceres

Saturday, 13 April 2013

• Re: [futures] Persistent/Repeated Future that doesn't resolve Jake Verbaten
• Re: [futures] Persistent/Repeated Future that doesn't resolve Tab Atkins Jr.

Friday, 12 April 2013

• Re: [futures] Add convenience functions for immediate/canceled promises Tab Atkins Jr.
• Re: [futures] Persistent/Repeated Future that doesn't resolve Tab Atkins Jr.
• Re: Fwd: [futures] Persistent/Repeated Future that doesn't resolve Brandon Wallace
• Fwd: [futures] Persistent/Repeated Future that doesn't resolve Jake Verbaten
• Re: [futures] Making ProgressFuture immediate Jake Verbaten
• Re: [futures] Persistent/Repeated Future that doesn't resolve Tab Atkins Jr.
• Re: [futures] Persistent/Repeated Future that doesn't resolve Tab Atkins Jr.
• Re: [futures] Add convenience functions for immediate/canceled promises Tab Atkins Jr.
• Re: [futures] Persistent/Repeated Future that doesn't resolve Bjoern Hoehrmann
• RE: [futures] Persistent/Repeated Future that doesn't resolve Domenic Denicola

Thursday, 11 April 2013

• RE: [futures] Add convenience functions for immediate/canceled promises Domenic Denicola
• Re: [futures] Add convenience functions for immediate/canceled promises Brandon Wallace
• [futures] Add convenience functions for immediate/canceled promises Tab Atkins Jr.
• [futures] Folding .progress() into .then() for ProgressFuture Tab Atkins Jr.
• [futures] Persistent/Repeated Future that doesn't resolve Tab Atkins Jr.
• [futures] Making ProgressFuture immediate Tab Atkins Jr.

Wednesday, 10 April 2013

• [Bug 21117] Define 'Break' and 'SysReq' key names bugzilla@jessica.w3.org

Tuesday, 9 April 2013

• [Bug 21338] Gut check on when to clear transient registered mutation observers bugzilla@jessica.w3.org
• [Bug 21635] "resolve" in Future example should probably be "resolver" bugzilla@jessica.w3.org
• [Bug 21635] New: "resolve" in Future example should probably be "resolver" bugzilla@jessica.w3.org

Monday, 8 April 2013

• [Bug 21626] TypeError is referenced, but not defined bugzilla@jessica.w3.org
• [Bug 21626] New: TypeError is referenced, but not defined bugzilla@jessica.w3.org

Friday, 5 April 2013

• Re: Future statics Anne van Kesteren
• Re: Future statics Brandon Wallace
• Future statics Anne van Kesteren

Thursday, 4 April 2013

• [Bug 5851] Consider adding .toArray() on NodeList and HTMLCollection bugzilla@jessica.w3.org

Tuesday, 2 April 2013

• [Bug 21522] New: Restore hasAttributes() bugzilla@jessica.w3.org

Last message date: Saturday, 29 June 2013 08:18:43 UTC