See also: IRC log
<trackbot> Date: 14 October 2009
<smaug> uh, only 1.47€ in my skype account
<smaug> I hope that is enough
<smaug> it should be
<smaug> Hi Travis
Sorry, I'm late...
<scribe> scribeNick: Travis
<scribe> scribe: Travis
All browsers (but perhaps Chrome?) use a number (rather than a Date object).
<shepazu> timeStamp of type DOMTimeStamp, readonly
<shepazu> Used to specify the time (in milliseconds relative to the epoch) at which the event was created. Due to the fact that some systems may not provide this information the value of timeStamp may be not available for all events. When not available, a value of 0 will be returned. Examples of epoch time are the time of the system start or 0:0:0 UTC 1st January 1970.
<shepazu> This read-only property is a Date object.
Probably relying on it as a sequence (for primitive ordering)
Can always new Date();
shepazu: Has been metioned that it's complicated for implementors to return a Date.
<smaug> new Date(event.timeStamp);
smaug: Can always convert timeStamp to date.
shepazu: Since IE is not
supporting this, there's likely little compat impact to
tightening up the spec.
... Could strip out the clause that allows zero.
<scribe> ACTION: shepazu to add "should" clause to make the timestamp an Epoch string of type Number (in the ECMAScript binding). [recorded in http://www.w3.org/2009/10/14-webapps-minutes.html#action01]
<trackbot> Created ACTION-417 - Add "should" clause to make the timestamp an Epoch string of type Number (in the ECMAScript binding). [on Doug Schepers - due 2009-10-21].
E.g., like the Progress Events 1.0 spec by Chaals?
shepazu: Sync and Async? SVG is just adding this concept.
I have to do this anyway... I may be able to provide this detail before November.
shepazu: Regarding the algorithms
of when to fire, that seems very host-language specific.
... sync/async, seems like a good idea to add to the spec.
<scribe> ACTION: Travis to provide async/ sync data based on browser testing [recorded in http://www.w3.org/2009/10/14-webapps-minutes.html#action02]
<trackbot> Created ACTION-418 - Provide async/ sync data based on browser testing [on Travis Leithead - due 2009-10-21].
shepazu: Event flow diagrams to
be added to spec soon.
... some combinations will be tricky.
Travis: Will DOM L3 Events support WebIDL syntax on its IDL blocks?
shepazu: Sam Wenieg will be co-editing WebIDL as Cameron finishes his disseration.
shepazu: Common myth that you
can't go to Rec with a normative reference to a non-Rec spec.
Actually not true, but requires greater scrutiny.
... We could "safely" use WebIDL in our spec.
shepazu: What do people think
about targeting last call for November?
... Have solicited early comments from other working groups to try to mitigate issues at Last Call.
shepazu: Added a section on
... Also a section on feature detection based on hasFeature
... Can you folks look this over and give me feedback?
Cameron and other have already provided feedback. Seems OK so far.
<shepazu> trackbot, make minutes
<trackbot> Sorry, shepazu, I don't understand 'trackbot, make minutes'. Please refer to http://www.w3.org/2005/06/tracker/irc for help
<shepazu> trackbot, end telcon
This is scribe.perl Revision: 1.135 of Date: 2009/03/02 03:52:20 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) Found ScribeNick: Travis Found Scribe: Travis Inferring ScribeNick: Travis Default Present: Shepazu, smaug, Travis Present: Shepazu smaug Travis WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Found Date: 14 Oct 2009 Guessing minutes URL: http://www.w3.org/2009/10/14-webapps-minutes.html People with action items: shepazu travis[End of scribe.perl diagnostic output]