W3C

- DRAFT -

Web Performance Working Group Teleconference

09 May 2012

See also: IRC log

Attendees

Present
+1.650.214.aaaa, [Microsoft], +1.650.253.aabb, Plh, Tony, Arvind, plh
Regrets
Chair
SV_MEETING_CHAIR
Scribe
JatinderMann_

Contents


<trackbot> Date: 09 May 2012

trackbot, start telecon

<trackbot> Meeting: Web Performance Working Group Teleconference

<trackbot> Date: 09 May 2012

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.

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.136 (CVS log)
$Date: 2012/05/09 17:33:17 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.136  of Date: 2011/05/12 12:01:43  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

No ScribeNick specified.  Guessing ScribeNick: JatinderMann_
Inferring Scribes: JatinderMann_
Default Present: +1.650.214.aaaa, [Microsoft], +1.650.253.aabb, Plh
Present: +1.650.214.aaaa [Microsoft] +1.650.253.aabb Plh Tony Arvind plh

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Found Date: 09 May 2012
Guessing minutes URL: http://www.w3.org/2012/05/09-webperf-minutes.html
People with action items: 

[End of scribe.perl diagnostic output]