Re: ISSUE-78: HTML5 stalled and suspend progress events [Progress Events]

2008-10-31 Thread Charles McCathieNevile
Cc'ed to SVG as well, since people there use progress events. Please reply to the Web Apps group (reply-to is set). On Sat, 25 Oct 2008 22:45:10 +0200, Web Applications Working Group Issue Tracker [EMAIL PROTECTED] wrote: ISSUE-78: HTML5 stalled and suspend progress events [Progress

Re: Call for Consensus - Selectors Last Call

2008-10-31 Thread Jonas Sicking
Hear hear! Charles McCathieNevile wrote: Hi, Lachy thinks the latest editor's draft[1] is ready for Last Call, after responding to all the comments from last time (and removing the NSResolver). The disposition of comments[2] explains what happened to those comments. So this is a call

Re: Call for Consensus - Selectors Last Call

2008-10-31 Thread Stewart Brodie
Kartikaya Gupta [EMAIL PROTECTED] wrote: On Fri, 31 Oct 2008 16:06:23 +0100, Charles McCathieNevile [EMAIL PROTECTED] wrote: So this is a call for Consensus to publish the Editor's Draft [1] of the Selectors API spec as a Last Call. Please respond before Monday November 10. As always,

Re: ISSUE-78: HTML5 stalled and suspend progress events [Progress Events]

2008-10-31 Thread Charles McCathieNevile
On Fri, 31 Oct 2008 19:31:50 +0100, Ian Hickson [EMAIL PROTECTED] wrote: On Fri, 31 Oct 2008, Charles McCathieNevile wrote: We have previously discussed a stalled event, in the context of suggested timing for producing progress events. We decided not to set a specific timing, because the use

Re: ISSUE-78: HTML5 stalled and suspend progress events [Progress Events]

2008-10-31 Thread Ian Hickson
On Fri, 31 Oct 2008, Charles McCathieNevile wrote: I think it also makes sense to add a note that conforming specs and uesr agents *should* use the events defined rather than something else with equivalent functionality. I'm not sure it makes sense to make that a *must*. I think it

Re: Call for Consensus - Selectors Last Call

2008-10-31 Thread Lachlan Hunt
Kartikaya Gupta wrote: On Fri, 31 Oct 2008 16:06:23 +0100, Charles McCathieNevile [EMAIL PROTECTED] wrote: [1] http://dev.w3.org/2006/webapi/selectors-api/ [2] Is it just me or is the scope element somewhat under-defined in the spec? The only mentions of it are in this sentence: If the

Re: Call for Consensus - Selectors Last Call

2008-10-31 Thread Lachlan Hunt
Stewart Brodie wrote: 1) What is the scope element for - it's only mentioned in one sentence? That statement has now been commented out (see my previous mail [1]) 2) Is an empty string actually a valid selector? If not, then the whole null/undefined is an empty string discussion is

Re: Call for Consensus - Selectors Last Call

2008-10-31 Thread Maciej Stachowiak
I support the publication as Last Call. On Oct 31, 2008, at 8:06 AM, Charles McCathieNevile wrote: Hi, Lachy thinks the latest editor's draft[1] is ready for Last Call, after responding to all the comments from last time (and removing the NSResolver). The disposition of comments[2]

Re: Call for Consensus - Selectors Last Call

2008-10-31 Thread Cameron McCormack
Charles McCathieNevile: So this is a call for Consensus to publish the Editor's Draft [1] of the Selectors API spec as a Last Call. Please respond before Monday November 10. As always, silence is taken as assent but an explicit response is preferred. I’m in favour of publishing. A few

Re: New Progress draft (1.25)...

2008-10-31 Thread Garrett Smith
On Fri, Oct 31, 2008 at 8:05 AM, Charles McCathieNevile [EMAIL PROTECTED] wrote: On Sat, 25 Oct 2008 09:08:56 +0200, Jonas Sicking [EMAIL PROTECTED] wrote: Garrett Smith wrote: On Fri, Oct 24, 2008 at 5:51 AM, Jonas Sicking [EMAIL PROTECTED] wrote: Garrett Smith wrote: I agree. Not sure