W3C home > Mailing lists > Public > www-dom@w3.org > October to December 2009

Minutes: DOM3 Events Telcon, Wednesday, 14 October 2009

From: Doug Schepers <schepers@w3.org>
Date: Wed, 21 Oct 2009 06:23:52 -0400
Message-ID: <4ADEE138.7040403@w3.org>
To: "www-dom@w3.org" <www-dom@w3.org>
http://www.w3.org/2009/10/14-webapps-minutes.html


              Web Applications Working Group Teleconference

14 Oct 2009

    See also: [2]IRC log

       [2] http://www.w3.org/2009/10/14-webapps-irc

Attendees

    Present
           Shepazu, smaug, Travis

    Regrets
    Chair
           SV_MEETING_CHAIR

    Scribe
           Travis

Contents

      * [3]Topics
          1. [4]timestamps
          2. [5]Defining Events in DOM3 Events
          3. [6]WebIDL for DOM L3 Events.
          4. [7]Last Call Timeline?
          5. [8]New sections to the spec
      * [9]Summary of Action Items
      _________________________________________________________



    <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> [10]http://mozilla.pettay.fi/moztests/timestamp.html

      [10] http://mozilla.pettay.fi/moztests/timestamp.html

    <smaug> Hi Travis

    Sorry, I'm late...

    <scribe> scribeNick: Travis

timestamps

    <scribe> scribe: Travis

    <smaug>
    [11]http://www.w3.org/TR/2000/REC-DOM-Level-2-Events-20001113/ecma-s
    cript-binding.html

      [11] 
http://www.w3.org/TR/2000/REC-DOM-Level-2-Events-20001113/ecma-script-binding.html

    All browsers (but perhaps Chrome?) use a number (rather than a Date
    object).

    <shepazu> [[

    <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> ]]

    <shepazu> [[

    <shepazu> timeStamp

    <shepazu> This read-only property is a Date object.

    <shepazu> ]]

    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
    [12]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].

Defining Events in DOM3 Events

    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
    [13]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.

WebIDL for DOM L3 Events.

    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.

    er, dissertation

    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.

Last Call Timeline?

    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.

New sections to the spec

    shepazu: Added a section on conformance criteria
    ... 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 [14]http://www.w3.org/2005/06/tracker/irc
    for help

      [14] http://www.w3.org/2005/06/tracker/irc

    <shepazu> trackbot, end telcon

Summary of Action Items

    [NEW] ACTION: shepazu to add "should" clause to make the timestamp
    an Epoch string of type Number (in the ECMAScript binding).
    [recorded in
    [15]http://www.w3.org/2009/10/14-webapps-minutes.html#action01]
    [NEW] ACTION: Travis to provide async/ sync data based on browser
    testing [recorded in
    [16]http://www.w3.org/2009/10/14-webapps-minutes.html#action02]
Received on Wednesday, 21 October 2009 10:23:57 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 22 June 2012 06:14:04 GMT