See also: IRC log
<trackbot> Date: 22 February 2012
<scribe> scribe: JatinderMann
<plh> actually, I can only be on irc today
Zhiheng updated the Resource Timing processing model Step 8
https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/ResourceTiming/Overview.html
JatindeR: To include cross-origin resource duration.
James: Changes look good.
Jatinder: I think that was the only item we had to discuss for Resource Timing.
Jatinder: Did anyone have a chance to read Alois' proposal?
James: Yes, I did read it.
Jatinder: Thoughts on the proposal?
James: I think there is too much information here to expose to the web platform. This seems like something better suited for Developer Tools.
Alois: If we feel that there is too much information, we may want to reduce the amount of information.
James: I always felt that User Timing is the place to measure script timing.
Karen: What about adding a resource timing attribute for downloading and parsing script resources.
James: I think you can still get parse time using User timing.
Karen: You still can't get third party script.
Jatinder: Let's step back, what is the goal of this feature?
Alois: I want to find out how
long third party script takes to download and run.
... Also, interested in script execution times...
<plh> I guess I'll have to check if we're ready to move to CR for Resource Timing
Jatinder: How does JIT compiling
play into this?
... What about security risks?
James: You can find more information on where a user has been or if a user is logged in based on script execution time.
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.
Alois: What about if I want to get Facebook timing or twitter timing?
James: Facebook can instrument their code with User Timign if they want you to get that timing information.
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.
... Seems like these are two different models of the same
thing.
Karen: Besides, we will need to make sure this new model is secure if we are to even consider it.
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.
James: I agree.
Jatinder: Regarding Anne's
comment on Page Visibility privacy -
http://lists.w3.org/Archives/Public/public-web-perf/2012Feb/0042.html
... I think we are in agreement that we can remove the optional
clause for a user agent to turning off the Page Visibility
API.
Arvind: Agree that it isn't necessary to be spec'd out.
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) Found Scribe: JatinderMann Inferring ScribeNick: JatinderMann Present: plh alois JatinderMann Arvind James WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Found Date: 22 Feb 2012 Guessing minutes URL: http://www.w3.org/2012/02/22-webperf-minutes.html People with action items:[End of scribe.perl diagnostic output]