18:03:01 <RRSAgent> RRSAgent has joined #webapps
18:03:02 <RRSAgent> logging to http://www.w3.org/2009/10/14-webapps-irc
18:03:03 <trackbot> RRSAgent, make logs public
18:03:04 <Zakim> Zakim has joined #webapps
18:03:05 <trackbot> Zakim, this will be WAPP
18:03:06 <Zakim> I do not see a conference matching that name scheduled within the next hour, trackbot
18:03:06 <trackbot> Meeting: Web Applications Working Group Teleconference
18:03:07 <trackbot> Date: 14 October 2009
18:03:26 <Zakim> IA_WebApps(DOM3)2:00PM has now started
18:03:27 <Zakim> +Shepazu
18:04:13 <smaug> uh, only 1.47€ in my skype account
18:04:17 <smaug> I hope that is enough
18:04:20 <smaug> it should be
18:04:55 <smaug_> smaug_ has left #webapps
18:05:07 <Zakim> +??P4
18:05:18 <smaug> Zakim, ??P4 is me
18:05:18 <Zakim> +smaug; got it
18:16:23 <smaug> http://mozilla.pettay.fi/moztests/timestamp.html
18:25:43 <Travis> Travis has joined #webapps
18:25:51 <smaug> Hi Travis
18:26:00 <Travis> Sorry, I'm late...
18:26:41 <Zakim> +[Microsoft]
18:27:10 <Travis> scribeNick: Travis
18:28:44 <shepazu> Zakim, [Microsoft] is Travis
18:28:44 <Zakim> +Travis; got it
18:28:45 <Travis> Topic: timestamps
18:29:12 <Travis> scribe: Travis
18:29:32 <smaug> http://www.w3.org/TR/2000/REC-DOM-Level-2-Events-20001113/ecma-script-binding.html
18:30:23 <Travis> All browsers (but perhaps Chrome?) use a number (rather than a Date object).
18:31:02 <shepazu> [[
18:31:04 <shepazu> timeStamp of type DOMTimeStamp, readonly
18:31:04 <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.
18:31:05 <shepazu> ]]
18:31:36 <shepazu> [[
18:31:38 <shepazu> timeStamp
18:31:38 <shepazu>     This read-only property is a Date object.
18:31:39 <shepazu> ]]
18:32:28 <Travis> Probably relying on it as a sequence (for primitive ordering)
18:32:53 <Travis> Can always new Date();
18:34:35 <Travis> shepazu: Has been metioned that it's complicated for implementors to return a Date.
18:35:08 <smaug> new Date(event.timeStamp);
18:35:12 <Travis> smaug: Can always convert timeStamp to date.
18:36:55 <Travis> shepazu: Since IE is not supporting this, there's likely little compat impact to tightening up the spec.
18:37:45 <Travis> ... Could strip out the clause that allows zero.
18:40:54 <Travis> Action: shepazu to add "should" clause to make the timestamp an Epoch string of type Number (in the ECMAScript binding).
18:40:54 <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].
18:41:26 <shepazu> Topic: Defining Events in DOM3 Events
18:43:18 <Travis> E.g., like the Progress Events 1.0 spec by Chaals?
18:45:42 <Travis> shepazu: Sync and Async? SVG is just adding this concept.
18:48:33 <Travis> I have to do this anyway... I may be able to provide this detail before November.
18:49:00 <Travis> shepazu: Regarding the algorithms of when to fire, that seems very host-language specific.
18:49:16 <Travis> shepazu: sync/async, seems like a good idea to add to the spec.
18:49:51 <Travis> Action: Travis to provide async/ sync data based on browser testing
18:49:51 <trackbot> Created ACTION-418 - Provide async/ sync data based on browser testing [on Travis Leithead - due 2009-10-21].
18:50:24 <Travis> shepazu: Event flow diagrams to be added to spec soon.
18:50:58 <Travis> ... some combinations will be tricky.
18:52:46 <Travis> Topic: WebIDL for DOM L3 Events.
18:53:30 <Travis> Travis: Will DOM L3 Events support WebIDL syntax on its IDL blocks?
18:57:31 <darobin> darobin has joined #webapps
19:00:22 <Travis> shepazu: Sam Wenieg will be co-editing WebIDL as Cameron finishes his disseration.
19:00:41 <Travis> er, dissertation
19:02:00 <Travis> 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.
19:02:37 <Travis> ... We could "safely" use WebIDL in our spec.
19:05:59 <Travis> Topic: Last Call Timeline?
19:06:28 <Travis> shepazu: What do people think about targeting last call for November?
19:07:17 <Travis> ... Have solicited early comments from other working groups to try to mitigate issues at Last Call.
19:08:42 <Travis> Topic: New sections to the spec
19:09:03 <Travis> shepazu: Added a section on conformance criteria
19:09:49 <Travis> ... Also a section on feature detection based on hasFeature
19:10:06 <Travis> ... Can you folks look this over and give me feedback?
19:10:23 <Travis> Cameron and other have already provided feedback. Seems OK so far.
19:10:54 <Zakim> -smaug
19:10:57 <Zakim> -Travis
19:11:01 <Zakim> -Shepazu
19:11:03 <Zakim> IA_WebApps(DOM3)2:00PM has ended
19:11:04 <Zakim> Attendees were Shepazu, smaug, Travis
19:34:45 <gsnedders> gsnedders has joined #webapps
19:36:15 <shepazu> trackbot, make minutes
19:36:15 <trackbot> Sorry, shepazu, I don't understand 'trackbot, make minutes'. Please refer to http://www.w3.org/2005/06/tracker/irc for help
19:36:25 <shepazu> trackbot, end telcon
19:36:25 <trackbot> Zakim, list attendees
19:36:25 <Zakim> sorry, trackbot, I don't know what conference this is
19:36:26 <trackbot> RRSAgent, please draft minutes
19:36:26 <RRSAgent> I have made the request to generate http://www.w3.org/2009/10/14-webapps-minutes.html trackbot
19:36:27 <trackbot> RRSAgent, bye
19:36:27 <RRSAgent> I see 2 open action items saved in http://www.w3.org/2009/10/14-webapps-actions.rdf :
19:36:27 <RRSAgent> ACTION: shepazu to add "should" clause to make the timestamp an Epoch string of type Number (in the ECMAScript binding). [1]
19:36:27 <RRSAgent>   recorded in http://www.w3.org/2009/10/14-webapps-irc#T18-40-54
19:36:27 <RRSAgent> ACTION: Travis to provide async/ sync data based on browser testing [2]
19:36:27 <RRSAgent>   recorded in http://www.w3.org/2009/10/14-webapps-irc#T18-49-51