20:00:31 RRSAgent has joined #webperf 20:00:31 logging to http://www.w3.org/2014/03/05-webperf-irc 20:00:33 RRSAgent, make logs world 20:00:33 Zakim has joined #webperf 20:00:35 Zakim, this will be WPWG 20:00:35 I do not see a conference matching that name scheduled within the next hour, trackbot 20:00:36 Meeting: Web Performance Working Group Teleconference 20:00:36 Date: 05 March 2014 20:01:49 present+ tobint 20:01:56 present+ JatinderMann 20:02:08 present+ Puneet 20:02:27 pmsangal has joined #webperf 20:04:04 plh has joined #webperf 20:04:18 zakim, this is per 20:04:18 ok, plh; that matches RWC_web-per()3:00PM 20:04:47 zakim, passcode? 20:04:48 the conference code is 97373 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), plh 20:05:17 +plh 20:05:36 present+ plh 20:07:49 https://www.w3.org/2010/webperf/track/agenda 20:07:54 topic: Open Actions 20:08:58 JatinderMann: Action item 73 looks like beacon - can we close 20:09:04 close action-73 20:09:04 Closed action-73. 20:09:20 action-97? 20:09:20 action-97 -- Tony Gentilcore to Check with Adam Barth on Memory Leak API -- due 2012-09-30 -- OPEN 20:09:20 http://www.w3.org/2010/webperf/track/actions/97 20:10:04 JatinderMann: Action Item 97. We've talked about this a number of times, but we likely should close this for now. We can come back to it later. 20:10:24 plh: There are some security issues here for now. I agree we should close. 20:10:33 close action-97 20:10:33 Closed action-97. 20:11:30 JatinderMann: This one keeps coming up. Should we close or open? 20:11:55 plh: We should likely lean toward keeping them open if we are not sure. We can follow up with the owner. 20:12:46 JatinderMann: You can switch between networks very rapidly (LTE, 3G, WiFi). You may check one network, but quickly end up on another network. Let's follow up with Alois. 20:12:56 plh: I agree. Let's check with Alois. 20:13:37 Puneet: Someone suggested that we should look at bytes transfered. 20:14:15 plh: Bytes transfered can change from one moment to the next as well. Maybe people should use information in resource timings. 20:14:35 JatinderMann: we talked about adding byte information to resource timing, but I don't think we've done that yet. 20:16:35 JatinderMann: Regarding Action 104: Resource Timing 1 doesn't include information for audio or video elements because they come down in chunks. 20:17:21 plh: Do we add XHR to resource timing? If so we should consider adding this. 20:17:30 JatinderMann: We do. 20:17:54 Jatinder: We should get this on the agenda at some point soon. 20:18:11 JatinderMann: Action 106. This one is on plh. 20:18:36 plh: I haven't done this yet. 20:18:53 JatinderMann: Action-111 onward are from TPAC 20:19:04 JatinderMann: Action-111: http://www.w3.org/2010/webperf/track/actions/111 20:19:38 JatinderMann: We decided to not have a limit and wait for implimentation. We should probably keep this open so we know it's still an issue. 20:20:03 plh: We could close the action and open an issue. 20:20:43 JatinderMann: Let's document that. Close the action item and open an issue. 20:20:55 plh: you can close the action item, I am looking at creating an issue. 20:21:07 close action-111 20:21:07 Closed action-111. 20:21:25 JatinderMann: Action-112: http://www.w3.org/2010/webperf/track/actions/112 20:22:20 JatinderMann: We should get it into a spec and get some more people looking at it for feedback. 20:22:44 JatinderMann: Let's keep it open until ig gets it into a spec. Let's assign this one to Ilya 20:23:44 JatinderMann: Action-113 should be done, but tobint will follow up to verify. http://www.w3.org/2010/webperf/track/actions/113 20:23:54 tobint: will do. 20:24:30 JatinderMann: Action-116. http://www.w3.org/2010/webperf/track/actions/116 20:25:06 JatinderMann: We might want a security review on this one. Can we do detailed error logging securely. 20:25:19 JatinderMann: Is there someone from w3c that we can loop in for a review? 20:25:27 plh: I have a name but I need to double check. 20:26:24 JatinderMann: Let's update the spec to do basic error logging and see if we can do detailed error logging later. 20:26:39 JatinderMann: Action item 117 http://www.w3.org/2010/webperf/track/actions/117 20:26:50 JatinderMann: Let's leave this one open. 20:27:05 JatinderMann: Action-118: http://www.w3.org/2010/webperf/track/actions/118 20:27:39 JatinderMann: plh will ping Mark tomorrow 20:27:48 plh: I'll do that tomorrow. 20:28:03 JatinderMann: Action-119: http://www.w3.org/2010/webperf/track/actions/119 20:28:20 JatdinerMann: This one is on tobin. We discussed this at TPAC. 20:29:13 JatinderMann: Action-120, 121, 122: Sounds like JavaScript injection thing. 20:29:33 JatinderMann: Let's ping Arvind on this. Tobin and I will follow up with Microsoft people. 20:29:45 JatinderMann: Action-123: That's on Arvind. We should ping him on that. 20:30:02 JatinderMann: Action-125: I think mark has already done this. We should take his proposal and update the spec. 20:30:17 http://lists.w3.org/Archives/Public/public-web-perf/2013Dec/0090.html 20:30:17 plh: Agree. 20:30:30 JatinderMann: We should put this on tobin to get him to update the spec. 20:31:22 JatinderMann: We might want a little more clarification. What does SDPY return today. Perhaps some examples of what we want. 20:31:29 plh: I think we talked about this in the past. 20:31:49 JatinderMann: Yes. We did. We will look into this and get back to the wg. 20:32:01 JatinderMann: Action-126 still open - assign to tobin 20:32:12 plh: Didn't we agree to drop postpone and go after lazyload. 20:32:23 plh: I think that was what we discussed at TPAC 20:32:36 JatinderMann: I think you're right. We should review TPAC notes to verify. 20:33:13 JatinderMann: I think we said we should drop postpone for now and kill the CSS property. 20:33:31 plh: We should update the action item title to match 20:34:03 JatinderMann: We should open an action item to remove postpone from resource priorities. 20:34:21 JatinderMann: That brings us up to date on TPAC. Will likely want to open more action items. 20:34:49 https://www.w3.org/2010/webperf/track/agenda 20:36:05 close issue-8 20:36:05 Closed issue-8. 20:36:08 JatinderMann: We can likely close Issue-8 20:36:13 plh: Agreed. 20:36:37 plh: Close issue 10 20:36:40 JatinderMann: Agreed 20:36:54 close issue-10 20:36:54 Closed issue-10. 20:37:08 JatinderMann: Issue-11 should be closed 20:37:11 close issue-11 20:37:11 Closed issue-11. 20:37:22 plh: agreed 20:38:57 plh: Add DOM events with high res time to agenda for next week 20:39:41 http://www.w3.org/wiki/Web_Performance/Publications 20:39:43 JatinderMann: we should do all of our work out of the action tracker: https://www.w3.org/2010/webperf/track/agenda 20:39:51 plh: Agreed. 20:41:31 plh: requestanimationframe need test cases to move spec from CR to PR 20:41:51 JatinderMann: We need to start a new push to get tests for these. 20:42:03 JatinderMann: we should probably send out a mail. 20:42:50 https://github.com/w3c/web-platform-tests/issues?labels=wg-webperf 20:43:03 plh: Yes. Here is a link which is useful for us to help us track test needs: https://github.com/w3c/web-platform-tests/issues?labels=wg-webperf 20:43:27 plh: Two of them are from Microsoft. 20:44:40 JatinderMann: once we get the tests, I think this can get us moved forward 20:48:54 Topic: Web Performance Guidance 20:49:10 plh: We should put a template together to allow us to build web performance guidance. 20:49:32 tobint: I'd love to help. I'm busy, as I'm sure others are, but am happy to help. 20:50:10 JatinderMann: I think it would be cool. Today we solve a bunch of problems and our APIs try to help solve a lot of these perf-related issues. 20:51:18 - +1.408.349.aaaa 20:51:20 -[Microsoft] 20:51:23 -plh 20:51:24 RWC_web-per()3:00PM has ended 20:51:24 Attendees were [Microsoft], +1.408.349.aaaa, plh 20:51:42 rrsagent, generate minutes 20:51:42 I have made the request to generate http://www.w3.org/2014/03/05-webperf-minutes.html tobint 21:46:23 pmsangal has joined #webperf 21:53:15 tobint has left #webperf 22:05:21 Zakim has left #webperf 22:57:55 pmsangal has left #webperf