18:01:17 RRSAgent has joined #webperf 18:01:17 logging to http://www.w3.org/2012/02/22-webperf-irc 18:01:19 RRSAgent, make logs world 18:01:19 Zakim has joined #webperf 18:01:21 Zakim, this will be WPWG 18:01:22 Meeting: Web Performance Working Group Teleconference 18:01:22 Date: 22 February 2012 18:01:23 I do not see a conference matching that name scheduled within the next hour, trackbot 18:01:25 scribe: JatinderMann 18:01:31 present+ plh 18:01:59 actually, I can only be on irc today 18:02:01 present+ alois 18:02:06 present+ JatinderMann 18:03:19 present+ Arvind 18:03:32 simonjam has joined #webperf 18:03:43 present+ James 18:06:46 Zhiheng updated the Resource Timing processing model Step 8 18:06:47 https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/ResourceTiming/Overview.html 18:06:59 JatindeR: To include cross-origin resource duration. 18:07:54 James: Changes look good. 18:08:53 Jatinder: I think that was the only item we had to discuss for Resource Timing. 18:09:02 Topic: JavaScript Timing 18:09:12 Jatinder: Did anyone have a chance to read Alois' proposal? 18:09:17 James: Yes, I did read it. 18:09:25 Jatinder: Thoughts on the proposal? 18:09:58 James: I think there is too much information here to expose to the web platform. This seems like something better suited for Developer Tools. 18:10:55 Alois: If we feel that there is too much information, we may want to reduce the amount of information. 18:11:12 James: I always felt that User Timing is the place to measure script timing. 18:11:29 Karen: What about adding a resource timing attribute for downloading and parsing script resources. 18:12:00 James: I think you can still get parse time using User timing. 18:12:14 Karen: You still can't get third party script. 18:15:04 Jatinder: Let's step back, what is the goal of this feature? 18:15:47 Alois: I want to find out how long third party script takes to download and run. 18:16:53 ...Also, interested in script execution times... 18:17:15 I guess I'll have to check if we're ready to move to CR for Resource Timing 18:19:29 Jatinder: How does JIT compiling play into this? 18:19:40 Jatinder: What about security risks? 18:20:15 James: You can find more information on where a user has been or if a user is logged in based on script execution time. 18:24:40 Jatinder: Seems like User Timing and JavaScript Timing are two different models for getting the same information. JavaScript Timing is post processing data - it gathers all data. User Timing is run time processing. 18:25:07 Alois: What about if I want to get Facebook timing or twitter timing? 18:25:23 James: Facebook can instrument their code with User Timign if they want you to get that timing information. 18:26:03 Jatinder: Even with a JavaScript Timing, third parties would need to give a CORS like header anyway. If they have to do that work anyway, they can just instrument their code with User Timing. 18:26:15 Jatinder: Seems like these are two different models of the same thing. 18:26:43 Karen: Besides, we will need to make sure this new model is secure if we are to even consider it. 18:35:26 Jatinder: I think User Timing and the new proposal are two different approaches for doing the same thing. I don't think we would add a new API that does the same thing as an existing API in a different way. 18:35:33 James: I agree. 18:35:44 Topic: Page Visibility 18:44:19 Jatinder: Regarding Anne's comment on Page Visibility privacy - http://lists.w3.org/Archives/Public/public-web-perf/2012Feb/0042.html 18:47:20 Jatinder: I think we are in agreement that we can remove the optional clause for a user agent to turning off the Page Visibility API. 18:51:23 Arvind: Agree that it isn't necessary to be spec'd out. 18:52:14 rrsagent, generate minutes 18:52:14 I have made the request to generate http://www.w3.org/2012/02/22-webperf-minutes.html JatinderMann 20:08:50 Zakim has left #webperf