ISSUE-148 (modularize d3e): Consider modularizing DOM3 Events [DOM3 Events]

ISSUE-148 (modularize d3e): Consider modularizing DOM3 Events [DOM3 Events] http://www.w3.org/2008/webapps/track/issues/148 Raised by: Doug Schepers On product: DOM3 Events Garrett Smith in : [[ I think we're all well aware of t

ISSUE-147 (event re-dispatching): re-dispatching an event that already has its flow started [DOM3 Events]

ISSUE-147 (event re-dispatching): re-dispatching an event that already has its flow started [DOM3 Events] http://www.w3.org/2008/webapps/track/issues/147 Raised by: Doug Schepers On product: DOM3 Events Sergey Ilinsky in : [[ I

ISSUE-146 (capture-phase targets): Capture-phase listeners invoked on targets [DOM3 Events]

ISSUE-146 (capture-phase targets): Capture-phase listeners invoked on targets [DOM3 Events] http://www.w3.org/2008/webapps/track/issues/146 Raised by: Doug Schepers On product: DOM3 Events Sergey Ilinsky in : [[ As far as I kno

ISSUE-145 (event handler ordering): Ordering event handlers registered by different means [DOM3 Events]

ISSUE-145 (event handler ordering): Ordering event handlers registered by different means [DOM3 Events] http://www.w3.org/2008/webapps/track/issues/145 Raised by: Doug Schepers On product: DOM3 Events Sergey Ilinsky in : [[ Has

ISSUE-144 (propagation exceptions): exceptions in handlers during event propagation [DOM3 Events]

ISSUE-144 (propagation exceptions): exceptions in handlers during event propagation [DOM3 Events] http://www.w3.org/2008/webapps/track/issues/144 Raised by: Doug Schepers On product: DOM3 Events Sergey Ilinsky in : [[ How do ex

ISSUE-143 (editorial d3e): DOM3 Events section 3 editorial errors [DOM3 Events]

ISSUE-143 (editorial d3e): DOM3 Events section 3 editorial errors [DOM3 Events] http://www.w3.org/2008/webapps/track/issues/143 Raised by: Doug Schepers On product: DOM3 Events Daniel Barclay : [[ In reading the Document Obje

ISSUE-142 (multiple keypress): one keydown might fire multiple keypress/textInput events [DOM3 Events]

ISSUE-142 (multiple keypress): one keydown might fire multiple keypress/textInput events [DOM3 Events] http://www.w3.org/2008/webapps/track/issues/142 Raised by: Doug Schepers On product: DOM3 Events Hallvord R. M. Steen : [[ S

ISSUE-141 (IME examples): IME examples [DOM3 Events]

ISSUE-141 (IME examples): IME examples [DOM3 Events] http://www.w3.org/2008/webapps/track/issues/141 Raised by: Doug Schepers On product: DOM3 Events Hallvord R. M. Steen : [[ In the text about Input Method Editors [1], the exam

ISSUE-140 (textInput keydown keypress): textInput event as default action of both keydown and keypress? [DOM3 Events]

ISSUE-140 (textInput keydown keypress): textInput event as default action of both keydown and keypress? [DOM3 Events] http://www.w3.org/2008/webapps/track/issues/140 Raised by: Doug Schepers On product: DOM3 Events Hallvord R. M. Steen

ISSUE-139 (clarify key repeat): Define which events repeat when a key is held down [DOM3 Events]

ISSUE-139 (clarify key repeat): Define which events repeat when a key is held down [DOM3 Events] http://www.w3.org/2008/webapps/track/issues/139 Raised by: Doug Schepers On product: DOM3 Events Hallvord R. M. Steen : [[ spec cu

ISSUE-138 (keyboard mapping): Define "keyboard mapping" [DOM3 Events]

ISSUE-138 (keyboard mapping): Define "keyboard mapping" [DOM3 Events] http://www.w3.org/2008/webapps/track/issues/138 Raised by: Doug Schepers On product: DOM3 Events Hallvord R. M. Steen : [[ what exactly does the spec mean whe

ISSUE-137 (IME-keypress): Should keypress events fire when using an IME? [DOM3 Events]

ISSUE-137 (IME-keypress): Should keypress events fire when using an IME? [DOM3 Events] http://www.w3.org/2008/webapps/track/issues/137 Raised by: Doug Schepers On product: DOM3 Events Hallvord R. M. Steen : [[ current spec text

ISSUE-136 (getCoordsAt): Consider adding MouseEvent.getCoordsAt(element)

ISSUE-136 (getCoordsAt): Consider adding MouseEvent.getCoordsAt(element) http://www.w3.org/2008/webapps/track/issues/136 Raised by: Doug Schepers On product: Jonathan Watt : [[ Background: Positioning elements based off the po

Re: [progress-events] Update

On Tue, 05 Oct 2010 19:36:27 +0200, Anne van Kesteren wrote: Thanks for taking this over Anne. On Tue, 05 Oct 2010 19:31:12 +0200, Olli Pettay wrote: May I ask why you think the interface member names are terrible? I should probably have left out that comment. It is just that they are

Re: Comment on Widget Interface...

hi Addison, On Thu, Sep 30, 2010 at 8:57 PM, Phillips, Addison wrote: >> Are you talking about a script using navigator.language? > > Not really, unless you expect navigator.language to be how widget containers > expose the runtime locale. > > Widget P&C describes how a widget is packaged (which

[Bug 10798] Find a new home for Selection

http://www.w3.org/Bugs/Public/show_bug.cgi?id=10798 Ms2ger changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED

RE: Seeking agenda items for WebApps' Nov 1-2 f2f meeting

I'm flexible. I will be at TPAC the entire week and will shift scheduling to attend the IndexedDB sessions. Cheers, Eliot > -Original Message- > From: public-webapps-requ...@w3.org [mailto:public-webapps- > requ...@w3.org] On Behalf Of Pablo Castro > Sent: Monday, October 04, 2010 8:03

Re: [progress-events] Update

On Tue, 05 Oct 2010 19:31:12 +0200, Olli Pettay wrote: May I ask why you think the interface member names are terrible? I should probably have left out that comment. It is just that they are inconsistent — lengthComputable vs total — and seem to imply a specific kind of process — loaded.

Re: [progress-events] Update

On 10/05/2010 07:22 PM, Anne van Kesteren wrote: I offered Charles to take over editing of the Progress Events specification and hopefully drive it to completion. Today I wrote a draft for ProgressEvent & company inspired by Charles' work: http://dev.w3.org/2006/webapi/progress/ I suggest we pu

[Bug 10382] [IndexedDB] Note on avoiding reader/writer starvation

http://www.w3.org/Bugs/Public/show_bug.cgi?id=10382 Eliot Graff changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|

[widgets] RfC: LCWD of Widget Packaging and Configuration; comment deadline October 26

This is a Request for Comments for the October 5 Last Call Working Draft (LCWD) of the Widget Packaging and Configuration spec: http://www.w3.org/TR/2010/WD-widgets-20101005/ The previous publication of this spec was a Candidate Recommendation (Dec 2009) and it returned to LCWD because

[progress-events] Update

I offered Charles to take over editing of the Progress Events specification and hopefully drive it to completion. Today I wrote a draft for ProgressEvent & company inspired by Charles' work: http://dev.w3.org/2006/webapi/progress/ I suggest we publish this as a Working Draft. Relative to

Re: Seeking agenda items for WebApps' Nov 1-2 f2f meeting

Given the feedback so far, I think we should consider the Tuesday afternoon time slots for Indexed Database API and the File * specs as confirmed: http://www.w3.org/2008/webapps/wiki/TPAC2010#Tuesday.2C_November_2 As such, I removed those two items from the Specs and Topics of Interest lis

Re: Comment on Widget Interface...

Hi Scott, Yes, that's it. Do you know why it was removed? Addison Sent from my iPhone On Oct 5, 2010, at 4:12 AM, "Scott Wilson" wrote: > > On 5 Oct 2010, at 01:28, Charles McCathieNevile wrote: > >> On Mon, 04 Oct 2010 23:32:46 +0200, Scott Wilson >> wrote: >> >>> Actually, just to tot

Re: Comment on Widget Interface...

On 5 Oct 2010, at 01:28, Charles McCathieNevile wrote: > On Mon, 04 Oct 2010 23:32:46 +0200, Scott Wilson > wrote: > >> Actually, just to totally contradict myself, we implemented the locale >> attribute of the Widget interface and forget to take it out again when it >> was removed from the