16:59:37 RRSAgent has joined #webperf 16:59:37 logging to http://www.w3.org/2013/05/29-webperf-irc 16:59:42 zakim, this is per 16:59:42 ok, plh; that matches RWC_web-per()1:00PM 16:59:49 JatinderMann has joined #webperf 16:59:58 +Plh 16:59:59 trackbot, start telecon 17:00:01 RRSAgent, make logs world 17:00:03 Zakim, this will be WPWG 17:00:03 I do not see a conference matching that name scheduled within the next hour, trackbot 17:00:04 Meeting: Web Performance Working Group Teleconference 17:00:04 Date: 29 May 2013 17:01:02 zakim, aaaa is Rob 17:01:02 +Rob; got it 17:01:04 AaronHeady has joined #WebPerf 17:01:11 zakim, Microsoft has Jatinder 17:01:11 +Jatinder; got it 17:01:17 present+ RobDickenson 17:01:24 present+ alois 17:01:29 present+ plh 17:01:40 +[Microsoft.a] 17:02:05 present+ AaronHeady 17:02:53 zakim, Microsoft.a has Aaron 17:02:53 +Aaron; got it 17:08:08 Agenda: Diagnostics: Preflight JS Injection 17:08:45 Alois: We had discussed last week that if you cannot reach the webpage, you can specify JavaScript code that will be called. 17:10:26 Alois: You would have a specific header, e.g., . The UA would store this page locally, and if in the future the page isn't loaded, then this code is run. 17:11:44 +Daniel 17:11:51 Alois: And this would use the same caching rules as other resources. 17:12:48 Jatinder: What about security issues with this? 17:16:15 Aaron: A malicious could use this to track or execute. My worry is that the script is executing on the client and it can send a lot of errors to the server. 17:17:40 Aaron: From Bing's point of view, we're more interested in the capture errors on the next load scenario. We worry that this feature may create new security issues that could increase server load. 17:19:33 Jatinder: I don't believe we have limitations in the web platform today where we can limit script execution based on origin. Today, any script added to a site, regardless of origin, is run the same way. 17:19:48 Jatinder: If there is a security concern, we should run this by our security folks 17:21:02 Alois: I think there is a real benefit of getting real time error data, but we should follow up with security folks. 17:22:13 Aaron: Alternatively, instead of JavaScript, the browser could send a specific code/header back to the server to indicate an issue. 17:22:21 Alois: JavaScript would provide more information. 17:22:44 Jatinder: Let's follow up with our security teams and get back to this. 17:23:11 Topic: JavaScript Profiling 17:23:34 Alois: We could use a Chrome dev tool type JavaScript profiler that would send up the JavaScript calltree. 17:24:16 Jatinder: Would you run this for all users? 17:24:43 https://docs.google.com/document/d/1Yw_qNMCnGsWQRsdcrifzh_kzFey-ThQ3yp-DmxuJxvg/edit#heading=h.4n2xf0vts8kq 17:26:03 Alois: The idea would be that if some user has a problem, you can send them a link and the user would click on the link and the browser would gather the JavaScript callstack. 17:26:17 Dan: This would seem like a lot of data to specify in the specification. 17:26:32 Alois: We can use the Chrome and IE dev tools as a start point. 17:27:19 Dan: This will probably be a lot of data. 17:28:19 Alois: You would turn this on by demand. You would turn this on based on after a user passes a certain thershold. This is kind of an extension of User Timing, where there would be more information to help debug. 17:29:45 Dan: Would the user need to give consent to send this data? 17:30:10 Alois: We can talk about the privacy concern, but using JavaScript as is today you can already get 80-90% of data. 17:31:09 Dan: You would want to make sure that we don't track the user through the web, e.g., by looking at the URL. 17:37:35 -Daniel 17:40:21 Jatinder: Is the core usecase the 'support call' scenario where someone calls to state they have an issue and somone uses this API to gather that information. 17:41:38 Alois: Yes, that's main the one. 17:41:46 Topic: Browser Activity Monitoring 17:43:22 Alois: An APIs that provides runtime metrics on rendering, layout, garbage collection, CPU utilization, GPU utilization, memory consumption, etc. 17:51:35 Jatinder: Have you used Windows Performance Analyzer? It uses ETW events to gather similar type of data. However, there is a lot of information and data to send up if you tried to do this on the web platform. 17:53:18 Jatinder: You'd want to put together a minimal list of metrics that develoeprs would find useful. I'd love to understand how much this is necessary compared to just dev tools. 17:54:51 Topic: Detailed Networking Diagnostics 17:57:47 Alois: The goal here is to provide more detailed networking information, like IP address, HTTP headers. There are privacy concerns here that would need to be figured out. 17:57:56 Topic: Event Hooking 18:00:00 -Rob 18:00:34 Alois: You can do this using script and user timing, but it would be easier to measure the end to end event timing by using an API to hook into events. This is lower priority compared to the other listed items. 18:00:44 Topic: Test Repository 18:06:20 -[Microsoft.a] 18:06:22 -Plh 18:06:23 -[Microsoft] 18:06:23 -Alois 18:06:23 RWC_web-per()1:00PM has ended 18:06:23 Attendees were Alois, Plh, +1.949.754.aaaa, Rob, Jatinder, [Microsoft], Aaron, Daniel 18:06:37 rrsagent, generate minutes 18:06:37 I have made the request to generate http://www.w3.org/2013/05/29-webperf-minutes.html JatinderMann 19:31:19 Zakim has left #webperf