[minutes] 2012-05-09 Web Performance WG Teleconference #72

Meeting Summary:



1.       Navigation Timing

a.       test_timing_attributes_order.htm and test_document_readiness_exist.htm

Philippe has integrated the changes Boris has submitted and updated the tests.



b.       Navigation Timing to PR

Considering the test cases issue had not been resolved until today, we did not have a call with the Director to move Navigation Timing to PR this week. Once Philippe is back from vacation, in mid-June, we will have the call with the Director. There are no blocking items for moving to PR.



2.       Resource Timing

a.       Resource Timing to CR

Per a call with the Director this morning, Resource Timing will be published as CR on May 22nd.



3.       High Resolution Time

a.       High Resolution Time to CR

Per a call with the Director this morning, User Timing will be published as CR on May 22nd.



4.       User Timing

a.       User Timing to LC

As of this week, the User Timing spec has been re-published in Last Call.



b.      getMarks returns Array

The getMarks method is spec'd to return an Associative Array in the following JSON format: { "mark1": [0.750, 1.125, 3.333], "mark2": [2.125] }. However, that format is not compatible with JavaScript Arrays. ACTION-103: getMarks should return object in JSON format, not Array on Jatinder to update the spec, https://www.w3.org/2010/webperf/track/actions/103.



5.       Performance Timeline

a.       Performance Timeline to LC

As of this week, Performance Timeline has been re-published in Last Call.


Detailed Notes:



Web Perf Teleconference #71 5/09/2012



IRC log: http://www.w3.org/2012/05/09-webperf-irc



Meeting Minutes: http://www.w3.org/2012/05/09-webperf-minutes.html



Attendees

Present for Navigation Timing, Resource Timing and User Timing (4-5PM EST/1-2PM PST)

Jatinder Mann, Philippe Le Hegaret, Arvind Jain, Tony Gentilcore


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

Meeting cancelled.



Scribe

Jatinder Mann



Contents

Agenda

1. Working Group status update - High Resolution Time and Resource Timing to CR

2. User Timing Feedback - getMarks returns an Array

3. Feedback on all other specifications

--------------------------------------------------------------------------------
Navigation Timing

plh: We need to close on the remaining Navigation Timing test case. I believe Tony has approved the tests in Action 99.

Jatinder: Boris wanted us to push out a patch that will fix the test for Firefox.

plh: I noticed a failure in Chrome 20 but not in Chrome 18.

Tony: I emailed on the mailing list, seems like it works in Chrome now.

Jatinder: I will follow up with Karen and work on integrating the patch and pushing it out.

plh: We should be able to push NT to PR in mid-June once the tests are done.
User TIming

JAtinder: http://dvcs.w3.org/hg/webperf/raw-file/tip/specs/UserTiming/Overview.html

Array nIf the markName argument is not specified, the method returns an associative Array. Each key in the Array is a mark name. The value associated with the mark name is an Array of DOMHighResTimeStamp time values for that mark. In JSON notation, the data structure will look similar to this: { "mark1": [0.750, 1.125, 3.333], "mark2": [2.125] }.n

Array nIf the markName argument is not specified, the method returns an associative Array. Each key in the Array is a mark name. The value associated with the mark name is an Array of DOMHighResTimeStamp time values for that mark. In JSON notation, the data structure will look similar to this: { "mark1": [0.750, 1.125, 3.333], "mark2": [2.125] }.n

<plh> http://dvcs.w3.org/hg/webperf/raw-file/tip/specs/UserTiming/Overview.html

Jatinder: I don't believe the JSON format we have defined is compatible with a JavaScript Array. Looks like we should either update the spec or the format; I think the format is good.

Tony: Yes, looks like we just forgot to update the spec.

Jatinder: I will mail out a suggested text.
Resource Timing

Jatinder: We had a call with the director today - Resource Timing and High Resolution Time have been approved to be moved to CR.

plh: Because of a moritorium on publications, these specs will officially move to CR on May 22.
Page Visibility

Jatinder: We have one remaining issue on the spec.
... As most parties have chime in on that issue, we are waiting to hear Google's opinion.

Arvind: We have discussed it internally. I will send out a write up of our thoughts this week.
RequestAnimationFrame

Jatinder: We have a few remaining open issues on the spec that need the editors to make updates.

plh: I will ping Cameron to see if he can close on those issues.