<trackbot> Date: 14 March 2012

scribe+ JatinderMann

<plh> trackbot-ng, start telcon

<trackbot> Meeting: Web Performance Working Group Teleconference

<trackbot> Date: 14 March 2012

Resource Timing

Jatinder: Zhihang and I have responded to all of the last call feedback on the mailing list.

Zhiheng: Jatinder, can you check in the resource timing diagram? I need the diagram to make changes to it.

Jatinder: Will do.

plh: I will review the Resource Timing LC feedback and make sure nothing was missed.

Jatinder: Once we have made the diagram change, I will email you to let you know that we are clear to move forward to CR.

User Timing

Jatinder: As I was responding to the User Timing feedback to reword the privacy section, I noticed that the current privacy section suggests that the getMarks and getMeasures functions will return empty Arrays when invoked from scripts originating from different origins and the PerformanceMark and PerformanceMeasure interfaces will zero out data for the startTime and duration attributes when invoked from scripts originating from different origins. As th
... Do we want to allow sites to be able to allow cross-origin scripts from accessing this information with a CORS-like HTTP header, like we did for Resource Timing?

Tony: Yes, that seems reasonable. Without providing the ability to make this information available cross-origin, the benefit of the feature might be limited.

Jatinder: Especially in scenarios where a site has many sub-domains.
... I will update the spec to include the CORS like header. Do we want to use the timing-allow-origin header for both resource timing and user timing or give them unique headers, so a person can choose to offer one or the other?

Tony: I don't think that degree of granularity will be necessary. If you trust a site to share one metric, you should be able to share the other metric.

Jatinder: I think its reasonable to have one header.

plh: If we make such a change, we will want security folks to review it. I recommend we move the spec back to last call to make sure this change gets reviewed.

Page Visibility

Jatinder: I had been chatted with developers regarding the Page Visibility spec, and I had recieved feedback on the firing of visibilitychange during the unload. Most developers were worried that this code is just redudant with unload and that we will just be introducing more code that will run on the unload slowing down page navigations. If the feedback was to tie this in closer with session history, we may do that.

Arvind: Yes, I was reluctant with firing the event during unload as it is redundant. I am not as familar with session history. We should ask Boris of his motivation for this change.

Jatinder: I will start a mail thread.

requestAnimationFrame

Jatinder: I had some feedback regarding the animationStartTime attribute mentioned in the editor's note in the spec. I will send mail on it to make sure the editor's see it.

Performance Timeline

Jatinder: We expect that Performance Timeline and Resource Timing will move towards CR, considering there are no open items remaining. User Timing and High Resolution Time are currently in LC, and if there is limited feedback, these should move along to CR shortly as well.

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: Joseph_Scheuhammer, [Microsoft], +1.650.253.aaaa, Plh
Present: Joseph_Scheuhammer [Microsoft] +1.650.253.aaaa Plh JatinderMann ZhihengWang ArvindJain TonyG plh

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

Found Date: 14 Mar 2012
Guessing minutes URL: http://www.w3.org/2012/03/14-webperf-minutes.html
People with action items: