www-dom@w3.org from January to March 2013 by author

Anne van Kesteren

• Re: DOM: Futures (Friday, 29 March)
• Re: DOM: Futures (Friday, 29 March)
• Re: DOM: Futures (Thursday, 28 March)
• DOM: Futures (Thursday, 28 March)
• Re: DOM 4 request (Monday, 11 March)
• Re: DOM 4 request (Monday, 11 March)
• Re: DOM 4 request (Monday, 11 March)
• Re: DOM 4 request (Monday, 11 March)
• Re: DOM 4 request (Monday, 11 March)
• Re: proposal for a new acceptNode() return value for TreeWalker. (Friday, 8 March)
• [ui-events] MouseEvent details (Tuesday, 12 February)
• Re: Better event listeners (Tuesday, 12 February)
• Re: Better event listeners (Tuesday, 12 February)
• Re: Event constructor defaults (Monday, 11 February)
• [DOM3EVENTS] initEvent() (Monday, 11 February)
• [DOM3Events] MouseEvent.buttons (Tuesday, 22 January)
• Re: hardware timestamp for DOM Events. (Tuesday, 22 January)
• Re: hardware timestamp for DOM Events. (Monday, 21 January)
• Re: [DOM3Events] Pointer Events request to change DOM 3 Events "button" type (Monday, 21 January)
• Re: hardware timestamp for DOM Events. (Monday, 21 January)
• Re: new DOM4 insertions methods and return values (Wednesday, 16 January)
• UI Events (Monday, 14 January)
• Re: Better event listeners (Friday, 11 January)
• Re: Better event listeners (Friday, 11 January)
• Re: Better event listeners (Thursday, 10 January)
• Re: Better event listeners (Thursday, 10 January)
• Re: Better event listeners (Thursday, 10 January)
• Re: Better event listeners (Thursday, 10 January)
• Re: Better event listeners (Tuesday, 8 January)
• Re: "DOM4 Events" name (was: RE: ReSpec BiblioDB Entry for DOM Level 4 Events) (Monday, 7 January)
• Re: "DOM4 Events" name (was: RE: ReSpec BiblioDB Entry for DOM Level 4 Events) (Monday, 7 January)
• Re: Better event listeners‏ (Monday, 7 January)
• Re: ReSpec BiblioDB Entry for DOM Level 4 Events (Monday, 7 January)
• Better event listeners (Saturday, 5 January)
• Re: ReSpec BiblioDB Entry for DOM Level 4 Events (Saturday, 5 January)

Arthur Barstow

• RfC: LCWD of Pointer Events; comment deadline March 19 (Tuesday, 19 February)
• [D3E] What is the plan for 6-Sep-2012 LC comment processing? (Tuesday, 15 January)
• Re: ReSpec BiblioDB Entry for DOM Level 4 Events (Monday, 7 January)

Ben Lerner

• Re: DOM 3 Events (and Modeling and Reasoning about DOM Events) (Tuesday, 8 January)
• DOM 3 Events (and Modeling and Reasoning about DOM Events) (Monday, 7 January)

Benoit Marchant

• Re: Better event listeners (Monday, 7 January)

Bjoern Hoehrmann

• Re: Better event listeners (Wednesday, 13 March)
• Re: [DOM3Events] MouseEvent.buttons (Wednesday, 6 February)
• Re: Keyboard events for accessible RIAs and Games (Thursday, 31 January)
• Re: [DOM3Events] Pointer Events request to change DOM 3 Events "button" type (Tuesday, 22 January)
• Re: [DOM3Events] Pointer Events request to change DOM 3 Events "button" type (Monday, 21 January)

Boris Zbarsky

• Re: [dom] Need to describe the interaction of adoptNode with prototype chains (Wednesday, 16 January)
• Re: new DOM4 insertions methods and return values (Wednesday, 16 January)
• Re: [dom] Need to describe the interaction of adoptNode with prototype chains (Tuesday, 15 January)
• Re: Better event listeners (Sunday, 6 January)

Brad Pettit

• RE: [D4E] KeyboardEvent.code and KeyboardEvent.queryKeyCap() are very strange spec (Wednesday, 13 March)
• RE: [D4E] KeyboardEvent.code and KeyboardEvent.queryKeyCap() are very strange spec (Monday, 11 March)
• RE: DOM Keyboard Event Level 3 questions about proposal (Thursday, 7 March)
• RE: DOM Keyboard Event Level 3 questions about proposal (Tuesday, 26 February)

Brandon Wallace

• Re: Better event listeners (Wednesday, 9 January)

brandon.wallace@yahoo.com

• Re: Better event listeners (Saturday, 16 March)
• Re: Better event listeners (Thursday, 10 January)

bugzilla@jessica.w3.org

• [Bug 21444] FutureResolver's resolve algorithm uses wrong resolver in new handlers (Sunday, 31 March)
• [Bug 21433] "AlreadyResolved" error name is not listed (Sunday, 31 March)
• [Bug 21444] New: FutureResolver's resolve algorithm uses wrong resolver in new handlers (Saturday, 30 March)
• [Bug 21433] New: "AlreadyResolved" error name is not listed (Friday, 29 March)
• [Bug 21427] Futures: use thenable (Thursday, 28 March)
• [Bug 21427] New: Futures: use thenable (Thursday, 28 March)
• [Bug 21424] Futures: rename `catch` (Thursday, 28 March)
• [Bug 21424] New: Futures: rename `catch` (Thursday, 28 March)
• [Bug 17529] Inserting multiple script elements using a document fragment isn't specified properly (Friday, 22 March)
• [Bug 21338] New: Gut check on when to clear transient registered mutation observers (Tuesday, 19 March)
• [Bug 21271] New: Node.childList and Element.attributes need to return the same object each time (Wednesday, 13 March)
• [Bug 20463] The otherwise clause for Document objects can point to the DOM standard instead. See bug 20390 for more details. (Thursday, 7 March)
• [Bug 21143] New: Define command key names for multimedia keyboard (Wednesday, 27 February)
• [Bug 21140] New: Define key names for keyboard layout change keys (Wednesday, 27 February)
• [Bug 21139] New: Define key name for Hankaku-Zenkaku key and Katakana-Hiragana key (Wednesday, 27 February)
• [Bug 21137] New: Define key names for game controller of Android (Wednesday, 27 February)
• [Bug 21136] New: Define Home key and Back key of Android smartphone (Wednesday, 27 February)
• [Bug 21135] New: Define 'Symbol' modifier (Wednesday, 27 February)
• [Bug 21134] New: Define key names which launches specific application (Wednesday, 27 February)
• [Bug 21121] New: Define mobile phone related keys (Tuesday, 26 February)
• [Bug 21120] New: Define TV or A/V remote controller's keys (Tuesday, 26 February)
• [Bug 21119] New: Define 'ZoomIn' key and 'ZoomOut' key (Tuesday, 26 February)
• [Bug 21118] New: Define power management related keys like 'Power' (Tuesday, 26 February)
• [Bug 21117] New: Define 'Break' and 'SysReq' key names (Tuesday, 26 February)
• [Bug 21116] New: Define 'SingleCandidate' key in the key name list (Tuesday, 26 February)
• [Bug 21115] New: Define 'Redo' key in the key name list (Tuesday, 26 February)
• [Bug 21114] New: Dead key names are not enough for Linux (Tuesday, 26 February)
• [Bug 21113] New: Should KeyboardEvent.char really be set control characters? E.g., Cancel, Esc, Backspace and Del (Tuesday, 26 February)
• [Bug 21078] EventInit should have default values for bubbles and cancelable (Friday, 22 February)
• [Bug 21083] New: Proposal key names for Android (Friday, 22 February)
• [Bug 21078] New: EventInit should have default values for bubbles and cancelable (Thursday, 21 February)
• [Bug 21068] event.isTrusted should be [Unforgeable] (Thursday, 21 February)
• [Bug 21068] New: event.isTrusted should be [Unforgeable] (Thursday, 21 February)
• [Bug 14141] Introduce a constructor for Range (Monday, 11 February)
• [Bug 20941] Treewalker previousNode algorithm seems wrong (Sunday, 10 February)
• [Bug 20941] New: Treewalker previousNode algorithm seems wrong (Sunday, 10 February)
• [Bug 20753] Add hook to createElement / createElementNS (Friday, 25 January)
• [Bug 20753] New: Add hook to createElement / createElementNS (Thursday, 24 January)
• [Bug 20720] New: The remove() method from Element Interface is overwritten in HTMLSelectElement Interface (Monday, 21 January)
• [Bug 20713] New: Consider speccing Event.srcElement (Sunday, 20 January)
• [Bug 20654] New: Have Range.surroundContents() work for partially contained nodes? (Saturday, 12 January)
• [Bug 20608] "suppress observers flag" (Wednesday, 9 January)
• [Bug 20608] New: "suppress observers flag" (Tuesday, 8 January)
• [Bug 20567] New: Change [[Prototype]] for concept-node-adopt? (Friday, 4 January)

Christian Biesinger

• FocusEvent - spec text inconsistency (Tuesday, 29 January)

Cornelia Barbucenescu

• [dom] (Monday, 18 February)

David Bruant

• Re: DOM: Futures (Thursday, 28 March)
• Re: Better event listeners (Saturday, 16 March)
• Re: Better event listeners (Thursday, 14 March)

Dimitri Glazkov

• Re: [ui-events] MouseEvent details (Tuesday, 12 February)

Dirk Schulze

• Re: DOM 4 request (Monday, 11 March)
• Re: DOM 4 request (Monday, 11 March)

Domenic Denicola

• Re: Better event listeners (Thursday, 10 January)
• RE: Better event listeners (Wednesday, 9 January)

Erik Arvidsson

• Re: Better event listeners‏ (Monday, 7 January)

Florian Bösch

• Re: [D4E] KeyboardEvent.code and KeyboardEvent.queryKeyCap() are very strange spec (Monday, 11 March)
• Re: [D4E] KeyboardEvent.code and KeyboardEvent.queryKeyCap() are very strange spec (Monday, 11 March)
• Re: [D4E] KeyboardEvent.code and KeyboardEvent.queryKeyCap() are very strange spec (Monday, 11 March)
• Re: [D4E] KeyboardEvent.code and KeyboardEvent.queryKeyCap() are very strange spec (Monday, 11 March)
• Re: [D4E] KeyboardEvent.code and KeyboardEvent.queryKeyCap() are very strange spec (Monday, 11 March)
• Re: [D4E] KeyboardEvent.code and KeyboardEvent.queryKeyCap() are very strange spec (Monday, 11 March)
• Re: DOM Keyboard Event Level 3 questions about proposal (Sunday, 10 March)
• Re: DOM Keyboard Event Level 3 questions about proposal (Thursday, 7 March)
• Re: DOM Keyboard Event Level 3 questions about proposal (Thursday, 7 March)
• Re: Re: Re: Keyboard events for accessible RIAs and Games (Thursday, 31 January)
• Re: Re: Re: Keyboard events for accessible RIAs and Games (Thursday, 31 January)
• Re: Re: Keyboard events for accessible RIAs and Games (Thursday, 31 January)
• Re: Keyboard events for accessible RIAs and Games (Thursday, 31 January)
• Re: DOM Keyboard Event Level 3 questions about proposal (discussion about shortcut key on web applications) (Thursday, 31 January)
• Keyboard events for accessible RIAs and Games (Wednesday, 30 January)

François REMY

• RE: Better event listeners (Saturday, 16 March)
• RE: Better event listeners‏ (Monday, 7 January)
• Re: Better event listeners‏ (Monday, 7 January)

Geoffrey Garen

• Re: [dom] Need to describe the interaction of adoptNode with prototype chains (Tuesday, 15 January)

Glenn Maynard

• Re: DOM: Futures (Thursday, 28 March)
• Re: Better event listeners (Monday, 18 February)
• Re: Better event listeners (Tuesday, 12 February)
• Re: Better event listeners (Tuesday, 12 February)
• Re: Better event listeners (Tuesday, 12 February)
• Re: Event constructor defaults (Monday, 11 February)
• Event constructor defaults (Monday, 11 February)
• Re: Better event listeners (Friday, 11 January)
• Re: Better event listeners (Friday, 11 January)
• Re: Better event listeners (Thursday, 10 January)
• Re: Better event listeners (Tuesday, 8 January)
• Re: Better event listeners (Tuesday, 8 January)
• Re: Better event listeners (Tuesday, 8 January)
• Re: DOM 3 Events (and Modeling and Reasoning about DOM Events) (Tuesday, 8 January)
• Re: Better event listeners (Tuesday, 8 January)
• Re: DOM 3 Events (and Modeling and Reasoning about DOM Events) (Monday, 7 January)
• Re: Better event listeners (Sunday, 6 January)
• Re: Better event listeners (Saturday, 5 January)

Hallvord R. M. Steen

• Re: [D4E] KeyboardEvent.code and KeyboardEvent.queryKeyCap() are very strange spec (Monday, 11 March)

Hallvord Reiar Michaelsen Steen

• Re: [D4E] KeyboardEvent.code and KeyboardEvent.queryKeyCap() are very strange spec (Thursday, 28 February)
• Re: Re: Re: Keyboard events for accessible RIAs and Games (Thursday, 31 January)
• Re: Re: Keyboard events for accessible RIAs and Games (Thursday, 31 January)

Ian Hickson

• Re: DOM 3 Events (and Modeling and Reasoning about DOM Events) (Friday, 11 January)

Jacob Rossi

• RE: Distinguishing input from multiple users (Tuesday, 26 March)
• RE: [DOM3Events] Pointer Events request to change DOM 3 Events "button" type (Thursday, 24 January)
• Re: [DOM3Events] Pointer Events request to change DOM 3 Events "button" type (Monday, 21 January)
• RE: "DOM4 Events" name (was: RE: ReSpec BiblioDB Entry for DOM Level 4 Events) (Monday, 7 January)
• RE: "DOM4 Events" name (was: RE: ReSpec BiblioDB Entry for DOM Level 4 Events) (Monday, 7 January)
• "DOM4 Events" name (was: RE: ReSpec BiblioDB Entry for DOM Level 4 Events) (Monday, 7 January)
• RE: ReSpec BiblioDB Entry for DOM Level 4 Events (Monday, 7 January)
• ReSpec BiblioDB Entry for DOM Level 4 Events (Saturday, 5 January)

Jake Verbaten

• Re: DOM: Futures (Thursday, 28 March)
• Re: new DOM4 insertions methods and return values (Wednesday, 16 January)
• Re: new DOM4 insertions methods and return values (Wednesday, 16 January)
• new DOM4 insertions methods and return values (Wednesday, 16 January)
• Re: Better event listeners (Thursday, 10 January)
• Re: Better event listeners (Thursday, 10 January)
• Re: Better event listeners (Tuesday, 8 January)
• Re: Better event listeners (Monday, 7 January)

James Graham

• Re: Better event listeners (Friday, 11 January)
• Re: Better event listeners (Friday, 11 January)

Jonas Sicking

• Re: Better event listeners (Thursday, 14 March)
• Re: Better event listeners (Thursday, 14 March)
• Re: Better event listeners (Thursday, 14 March)
• Re: Better event listeners (Wednesday, 13 March)
• Re: Better event listeners (Friday, 18 January)
• Re: Better event listeners (Thursday, 10 January)

Marcos Caceres

• Re: Better event listeners (Monday, 7 January)
• Re: ReSpec BiblioDB Entry for DOM Level 4 Events (Monday, 7 January)
• Re: Better event listeners (Saturday, 5 January)
• Re: ReSpec BiblioDB Entry for DOM Level 4 Events (Saturday, 5 January)

Masayuki Nakano

• Re: [D4E] KeyboardEvent.code and KeyboardEvent.queryKeyCap() are very strange spec (Monday, 11 March)
• Re: DOM Keyboard Event Level 3 questions about proposal (Monday, 11 March)
• [D4E] KeyboardEvent.code and KeyboardEvent.queryKeyCap() are very strange spec (Thursday, 28 February)
• Re: DOM Keyboard Event Level 3 questions about proposal (Tuesday, 26 February)
• Re: DOM Keyboard Event Level 3 questions about proposal (Tuesday, 26 February)
• Re: DOM Keyboard Event Level 3 questions about proposal (Thursday, 31 January)
• Re: DOM Keyboard Event Level 3 questions about proposal (discussion about shortcut key on web applications) (Thursday, 31 January)

Mike Taylor

• Re: [AutoSafe Experience SRL] Promotie speciala (Thursday, 31 January)

Mounir Lamouri

• Re: Better event listeners (Wednesday, 27 March)

Ms2ger

• Re: new DOM4 insertions methods and return values (Wednesday, 16 January)

Ojan Vafai

• Re: [DOM3 Events] relatedTarget on blur/focus (Thursday, 7 February)

Olli Pettay

• Re: Better event listeners (Thursday, 14 March)
• Re: Better event listeners (Tuesday, 8 January)
• Re: Better event listeners (Sunday, 6 January)
• Re: Better event listeners (Sunday, 6 January)
• Re: Better event listeners (Saturday, 5 January)

Philippe Le Hegaret

• Re: hardware timestamp for DOM Events. (Monday, 21 January)

Richard Schwerdtfeger

• Re: DOM 4 request (Monday, 11 March)
• Re: DOM 4 request (Monday, 11 March)
• DOM 4 request (Saturday, 9 March)

Rick Waldron

• Re: Better event listeners (Thursday, 10 January)
• Re: Better event listeners (Monday, 7 January)

Robin Berjon

• Re: Better event listeners (Thursday, 10 January)

Sangwhan Moon

• Re: Distinguishing input from multiple users (Saturday, 30 March)

Sean Hogan

• Re: Better event listeners (Monday, 18 February)
• Re: Better event listeners (Monday, 18 February)

Tab Atkins Jr.

• Re: DOM: Futures (Thursday, 28 March)

Travis Leithead

• RE: [D3E] What is the plan for 6-Sep-2012 LC comment processing? (Monday, 21 January)
• RE: hardware timestamp for DOM Events. (Monday, 21 January)
• [DOM3Events] Pointer Events request to change DOM 3 Events "button" type (Monday, 21 January)
• hardware timestamp for DOM Events. (Monday, 21 January)
• RE: "DOM4 Events" name (was: RE: ReSpec BiblioDB Entry for DOM Level 4 Events) (Monday, 7 January)

Wez

• Re: [D4E] KeyboardEvent.code and KeyboardEvent.queryKeyCap() are very strange spec (Monday, 11 March)
• Re: [D4E] KeyboardEvent.code and KeyboardEvent.queryKeyCap() are very strange spec (Monday, 11 March)
• Re: [D4E] KeyboardEvent.code and KeyboardEvent.queryKeyCap() are very strange spec (Monday, 11 March)
• Re: [D4E] KeyboardEvent.code and KeyboardEvent.queryKeyCap() are very strange spec (Monday, 11 March)
• Re: [D4E] KeyboardEvent.code and KeyboardEvent.queryKeyCap() are very strange spec (Monday, 11 March)
• Re: DOM Keyboard Event Level 3 questions about proposal (Monday, 11 March)
• Re: DOM Keyboard Event Level 3 questions about proposal (Thursday, 7 March)
• Re: Re: Re: Keyboard events for accessible RIAs and Games (Thursday, 31 January)
• Re: Re: Keyboard events for accessible RIAs and Games (Thursday, 31 January)

Егор Николаев

• Re: DOM Keyboard Event Level 3 questions about proposal (Monday, 11 March)
• Re: DOM Keyboard Event Level 3 questions about proposal (Sunday, 10 March)
• Re: DOM Keyboard Event Level 3 questions about proposal (Thursday, 7 March)
• Re: DOM Keyboard Event Level 3 questions about proposal (discussion about shortcut key on web applications) (Tuesday, 5 February)
• Re: DOM Keyboard Event Level 3 questions about proposal (discussion about shortcut key on web applications) (Tuesday, 5 February)
• Re: DOM Keyboard Event Level 3 questions about proposal (Tuesday, 5 February)

Кошмарчик

• Re: [D4E] KeyboardEvent.code and KeyboardEvent.queryKeyCap() are very strange spec (Wednesday, 13 March)
• Re: DOM Keyboard Event Level 3 questions about proposal (Thursday, 7 March)
• Re: [D4E] KeyboardEvent.code and KeyboardEvent.queryKeyCap() are very strange spec (Friday, 1 March)
• Re: DOM Keyboard Event Level 3 questions about proposal (Tuesday, 26 February)
• Re: Re: Keyboard events for accessible RIAs and Games (Thursday, 31 January)

Last message date: Sunday, 31 March 2013 12:50:48 UTC