17:00:23 RRSAgent has joined #webperf 17:00:23 logging to http://www.w3.org/2013/08/07-webperf-irc 17:00:25 RRSAgent, make logs world 17:00:25 Zakim has joined #webperf 17:00:27 Zakim, this will be WPWG 17:00:28 Meeting: Web Performance Working Group Teleconference 17:00:28 Date: 07 August 2013 17:00:29 I do not see a conference matching that name scheduled within the next hour, trackbot 17:00:35 present+ JatinderMann 17:00:58 plh has joined #webperf 17:01:05 zakim, this is per 17:01:05 plh, I see RWC_web-per()1:00PM in the schedule but not yet started. Perhaps you mean "this will be per". 17:01:11 zakim, this will be per 17:01:12 ok, plh; I see RWC_web-per()1:00PM scheduled to start now 17:01:18 RWC_web-per()1:00PM has now started 17:01:19 +Plh 17:01:31 Alois has joined #webperf 17:01:44 +[Microsoft] 17:01:47 -Plh 17:01:48 +Plh 17:02:28 +Daniel 17:02:42 present+ plh 17:02:47 present+ Daniel 17:05:33 + +1.408.203.aaaa 17:06:05 present+ Arvind 17:06:51 Agenda: RequestionAnimationFrame, Resource Timing Update, New Specs to FPWD, and JS Preinjection 17:07:11 Topic: RequestAnimationFrame 17:07:59 Plh: Current text: Whenever a Document's hidden attribute is false and the animation frame request callback list is not empty, the user agent MUST regularly queue a task that samples all animations for that Document's top-level browsing context. 17:08:49 Plh: Proposed text: Whenever a Document's hidden attribute is false and the animation frame request callback list is not empty, the user agent MUST regularly queue a task that samples all animations for that Document's top-level browsing context unless the user agent is able to determine that the impacted elements are hidden. 17:08:59 + +43.732.908.2aabb 17:12:34 Jatinder: I can think of several cases where nothing is displayed 17:13:46 ... in the past, we don't have a clear meaning from page visibility 17:14:03 ... but leaving it open would be fine by me if it resolved Boris' concern 17:15:34 ... this is generic enough for v1 or we can revisite in v2 17:16:01 Topic: Resource Timing 17:18:00 Jatinder: I've updated onresourcetimingbufferfull to be an EventHandler 17:20:14 Plh: Once this change has been reviewed we can move to LC and get more review. We can then push from LC to PR directly. 17:27:10 Jatinder: I've looked at the test cases, and there are some failures in both IE and Chrome, test harness time outs, and some duplicate tests. We should verify if the test cases have been fixed, and if so, if the remaining issues are browser bugs, test case bugs, or spec bugs prior to moving Resource/User Timing to PR. 17:29:37 Topic: JS Preinjection 17:31:07 Jatinder: I wanted to talk about the goals: The monitoring JavaScript becomes a single point of failure for the page if it does not load, Modification of page source can result in unwanted side effects, The monitoring JavaScript will not be loaded when the page cannot be loaded (e.g. because of a DNS error), It does not allow to collect performance data for non-HTML request (e.g. images, pdf downloads) 17:31:49 Jatinder: Only #3 seems like the one we had discussed, I want to understand what these other use cases are for 17:34:01 - +1.408.203.aaaa 17:47:19 -[Microsoft] 17:47:20 -Daniel 17:47:21 - +43.732.908.2aabb 17:47:24 -Plh 17:47:25 RWC_web-per()1:00PM has ended 17:47:25 Attendees were Plh, [Microsoft], Daniel, +1.408.203.aaaa, +43.732.908.2aabb 17:47:43 Alois: The first one is general case of JavaScript can impact page load. The second one is that depending on when you add the script to the page, you can get side effects. 17:47:57 Jatinder: I'd like to see some examples of those side effects. 17:48:01 Alois: I can provide that. 17:49:34 Jatinder: The second use case looks like it's more related to RUM monitoring, where you are detouring and instrumenting sites. Site or library owners can add User Timing directly in their code, and avoid the oberver effect of having to detour code; technically, the detouring will slow down their page load. 17:50:44 JatinderMann_ has joined #webperf 17:51:10 Jatinder: The third bullet was the main goal from my point of view for this feature. As for the fourth bullet, Resource Timing does give you the image data. 17:51:30 Alois: The PDF download isn't associated with a Document, so that one might be missed. 17:52:23 Jatinder: We may want to consider that with Resource Timing L2, where downloads referred from a page are included in the timeline. It's not linked to the page load, but may be an interesting network perf data point. 17:52:40 Jatinder: I still need to have our security team review this spec. Once I have that review, I can provide more feedback. 17:52:48 Topic: Specs to FPWD 17:53:07 Jatinder: I have updated Beacon API spec with the working group feedback. I'd like to move this spec to FPWD. 17:53:12 Plh: I agree. 17:53:15 Dan: I agree as well. 17:53:43 Jatinder: I will be making updates to Resource Priorities, Navigation and Resource Errors next to get them ready for FPWD. 17:53:56 Topic: Web Perf Site Design 17:54:14 Jatinder: Plh, can we add the browser test case passing table to the site? Is this automated or manual? 17:54:49 Plh: The test case table is currently manually generated. We can look into doing that. If there are any updates you want to make to the site, do suggest or feel free to propose changes. 17:54:58 Topic: Next Meeting 17:55:05 Plh: I will be out next week on vacation. 17:55:10 Alois: So will I. 17:55:20 Jatinder: Let's schedule the next web perf meeting for two weeks from now. 17:55:25 rrsagent, generate minutes 17:55:25 I have made the request to generate http://www.w3.org/2013/08/07-webperf-minutes.html JatinderMann_ 19:16:29 Zakim has left #webperf