[minutes] 20110727 Web Performance WG Teleconference #43

Meeting Summary:



1.      Discussed feedback on Performance Timeline, Navigation Timing, Resource Timing and User Timing.

a.       Performance Timeline, Navigation Timing, Resource Timing and User Timing spec updates

The WG is happy with the changes made to the Timing specs. Accordingly, ACTION-41 and 42 have been closed. With these changes, Navigation Timing spec will return to its previous state of CR and will not need to go to last call, as no major changes have been made.



b.       Performance Timeline and User Timing specs to be published as First Public Working Drafts

The WG has agreed to publish Performance Timeline and User Timing specs as First Public Working Drafts.



c.        Performance Timeline, Resource Timing and User Timing specs to go into Last Call

The WG has agreed to take Performance Timeline, Resource Timing and User Timing specs into Last Call on August 8, 2011. This period will last until August 31, 2011.



d.       Evaluate using typed arrays from WebIDL spec in the Timing specs

We have opened ACTION-45 to evaluate updating the Timing specs to use typed arrays (T[]) from the Web IDL spec.



2.      Discuss requestAnimationFrame open issues

a.       The following open issues of the requestAnimationFrame spec remain:


1.       ISSUE-1: Scheduling processing model needs to be more tightly defined

Spec updated. Issue closed.



2.       ISSUE-2: Callback time parameter needs definition

3.       ISSUE-3: Animation frame times should be monotonically increasing

Editor working on updates.


4.       ISSUE-4: We perhaps should support an element parameter to requestAnimationFrame()

Remaining an open issue.


5.       ISSUE-5: Expected callback rates should be documented

Spec updated. Issue closed.


We had the following action items from this meeting:

1.       Jatinder Mann: ACTION-45: evaluate updating the Timing specs to use typed arrays (T[]) from the Web IDL spec.

2.       Philippe Le Hegaret: Publish Performance Timeline and User Timing specs as First Public Working Draft as soon as possible.

3.       Philippe Le Hegaret: Take Performance Timeline, Resource Timing and User Timing to Last Call on August 8th, 2011.

4.       Cameron McCormack and James Robinson: Resolve requestAnimationFrame spec open issues.



Detailed Notes:



Web Perf Teleconference #42 7/27/2011



IRC log: http://www.w3.org/2011/07/27-webperf-irc


Meeting Minutes: http://www.w3.org/2011/07/27-webperf-minutes.html



Attendees

Present for Navigation Timing, Resource Timing and User Timing (4-5PM EST/1-2PM PST)
Tony Gentilcore, James Simenson, Jatinder Mann, Nic Jansma, Arvind Jain


Present for Page Visibility, Efficient Script Yielding, Display Paint Notifications (4-5PM EST/2-3PM PST)
Jatinder Mann



Scribe

Jatinder Mann



Contents

Agenda

1.       Discuss updates to Performance Timeline, Navigation Timing, Resource Timing and User Timing specifications.

2.       Discuss progress on requestAnimationFrame open items.

3.       Any other business.



--------------------------------------------------------------------------------
Discuss updates to Performance Timeline, Navigation Timing, Resource Timing and User Timing specifications.
Jatinder: The WG has agreed to publish Performance Timeline and User Timing specs as FPWD.
... Has everyone looked at the changes?
Tony: Changes look good.
Jatinder: Should we setup a timeline to take these specs to Last Call? I would recommend taking Performance Timeline, Resource Timing and User Timing specs into Last Call on August 8, 2011. Thoughts?
Tony: We were wondering whether we should hold to go into last call until we start looking at implementation.
Jatinder: We have started looking at implementations and haven't seen any issues yet.
Tony: What is the process for going to CR? Don't we need two implementations to enter CR?
Jatinder: Yes, I believe that is the case for entering CR. I'm not sure what state the specs would be if we go to last call without two implementations.
Arvind: The specs can go to last call. After last call, if there are not two implementations, they will go to call for implementations. Once two implementations are available, the specs will then move to candidate recommendation.
Jatinder: That makes sense. In that case, shall we go to last call?
Arvind: Yes, let's do it.
Tony: I'm not against.
Jatinder: The WG has agreed to take Performance Timeline, Resource Timing and User Timing specs into Last Call on August 8, 2011. This period will last at least until August 31, 2011. We may want to move the last call period to 6 weeks in case there are a lot of August vacations.
... Is there any other business we want to discuss?
Tony: There was one small issue. While reading the webIDL spec, I noticed that typed arrays (T[]) might be something interesting to consider for these specs. What are your thoughts?
Jatinder: I'm sorry, I haven't read that portion of the WebIDL spec yet. We should probably all read the WebIDL spec and discuss futher if we want to consider typed arrays. I will open an action item to look into to typed arrays.
Action Jatinder to look into updating the Timing specs to use typed arrays (T[]) from the Web IDL spec.
<trackbot> Created ACTION-45 - Look into updating the Timing specs to use typed arrays (T[]) from the Web IDL spec. [on Jatinder Mann - due 2011-08-03].