17:01:36 RRSAgent has joined #webperf 17:01:36 logging to http://www.w3.org/2012/03/14-webperf-irc 17:01:38 RRSAgent, make logs world 17:01:38 Zakim has joined #webperf 17:01:40 Zakim, this will be WPWG 17:01:40 I do not see a conference matching that name scheduled within the next hour, trackbot 17:01:41 Meeting: Web Performance Working Group Teleconference 17:01:41 Date: 14 March 2012 17:02:26 zhiheng has joined #webperf 17:02:33 scribe+ JatinderMann 17:02:38 present+ JatinderMann 17:02:48 present+ ZhihengWang 17:02:53 present+ ArvindJain 17:04:44 present+ TonyG 17:05:17 plh has joined #webperf 17:05:23 trackbot-ng, start telcon 17:05:25 RRSAgent, make logs world 17:05:27 Zakim, this will be WPWG 17:05:27 I do not see a conference matching that name scheduled within the next hour, trackbot 17:05:28 Meeting: Web Performance Working Group Teleconference 17:05:28 Date: 14 March 2012 17:05:35 zakim, list conferences 17:05:35 I see T&S_Track(dnt)12:00PM, RWC_web-per()1:00PM, XML_EXI()12:30PM, WAI_PF()12:00PM, Team_(wai-testing)16:58Z active 17:05:37 also scheduled at this time is INC_(CGINF)1:00PM 17:05:39 zakim, this is per 17:05:39 ok, plh; that matches RWC_web-per()1:00PM 17:05:40 present+ plh 17:05:42 +Plh 17:08:53 Topic: Resource Timing 17:16:32 -Joseph_Scheuhammer.a 17:16:36 -Joseph_Scheuhammer 17:33:05 - +1.650.253.aaaa 17:33:06 -[Microsoft] 17:33:06 -Plh 17:33:07 RWC_web-per()1:00PM has ended 17:33:07 Attendees were Joseph_Scheuhammer, [Microsoft], +1.650.253.aaaa, Plh 17:36:07 Jatinder: Zhihang and I have responded to all of the last call feedback on the mailing list. 17:36:28 Zhiheng: Jatinder, can you check in the resource timing diagram? I need the diagram to make changes to it. 17:36:32 Jatinder: Will do. 17:36:58 plh: I will review the Resource Timing LC feedback and make sure nothing was missed. 17:37:29 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. 17:37:32 Topic: User Timing 17:38:18 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 17:38:50 ...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? 17:39:29 Tony: Yes, that seems reasonable. Without providing the ability to make this information available cross-origin, the benefit of the feature might be limited. 17:39:48 Jatinder: Especially in scenarios where a site has many sub-domains. 17:40:32 Jatinder: 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? 17:41:02 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. 17:41:22 Jatinder: I think its reasonable to have one header. 17:41:54 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. 17:42:04 Topic: Page Visibility 17:43:35 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. 17:48:27 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. 17:49:23 Jatinder: I will start a mail thread. 17:49:28 Topic: requestAnimationFrame 17:49:56 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. 17:50:21 Topic: Performance Timeline 17:51:21 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. 17:51:26 rrsagent, generate minutes 17:51:26 I have made the request to generate http://www.w3.org/2012/03/14-webperf-minutes.html JatinderMann