16:55:38 RRSAgent has joined #webperf 16:55:38 logging to http://www.w3.org/2013/03/20-webperf-irc 16:55:40 RRSAgent, make logs world 16:55:41 Zakim has joined #webperf 16:55:42 Zakim, this will be WPWG 16:55:43 Meeting: Web Performance Working Group Teleconference 16:55:43 Date: 20 March 2013 16:55:44 I do not see a conference matching that name scheduled within the next hour, trackbot 17:00:56 plh has joined #webperf 17:01:02 zakim, this is per 17:01:04 ok, plh; that matches RWC_web-per()1:00PM 17:01:11 +Plh 17:01:22 simonjam has joined #webperf 17:01:44 + +1.720.746.aabb 17:01:48 present+ JatinderMann, plh, simonjam 17:02:03 Alois has joined #webperf 17:02:08 present+ RobDickenson, DanielAustin 17:02:17 present+ Alois 17:03:04 zakim, aabb is Rob 17:03:04 +Rob; got it 17:03:09 zakim, aaaa is Daniel 17:03:09 +Daniel; got it 17:03:58 simonjam_ has joined #webperf 17:04:09 + +1.650.701.aacc 17:04:31 + +43.732.908.2aadd 17:04:37 zakim, aacc is James 17:04:37 +James; got it 17:04:51 zakim, James is really Arvind 17:04:51 +Arvind; got it 17:05:06 i keep getting "this passcode is not valid" 17:05:09 did it change? 17:05:10 -Arvind 17:05:13 zakim, passcode? 17:05:13 the conference code is 97373 (tel:+1.617.761.6200 sip:zakim@voip.w3.org), plh 17:05:26 that's what i'm trying :( 17:05:46 + +1.408.203.aaee 17:05:54 type 0 and one of our folks should be able to help 17:06:01 ganesh has joined #webperf 17:06:11 present+ Ganesh 17:06:35 +[GVoice] 17:06:40 + +1.503.264.aaff 17:07:00 present+ Ritika 17:07:12 Topic: Prerender 17:07:49 zakim, aaff is ganesh 17:07:49 +ganesh; got it 17:09:33 Jatinder: Things that I believe we should standardize in the Prerender spec are the tag definitions (e.g., Link rel="prerender" and Link rel="prefetch"), Page Visibility impact (e.g., document.visibilitystate must equal "prerender" at the time the page prerenders), and also consider adding a HTTP request header to identify prerender requests. 17:13:19 Arvind: About the HTTP header, we came up with page visibility as the primary means for the page owner to understand how to behave when the page is prerendered. 17:14:09 Jatinder: I agree on the concept of page owners using Page Visibility as the script means. What about the page load impact on servers? With a http header, the server could decide to throw away the request. 17:15:14 Arvind: We saw with prefetch that some sites didn't like the prefetch. For examples, some sites were sending 200 response code but were sending a broken page. 17:15:59 Ritika: We can always send a 404 response code to indicate that the site is broken to indicate to the man in the middle that the prerender isn't happening. 17:17:15 Arvind: Yes, we considered that, but 404 is still a valid code for page not existing. We thought of instead of creating a new prerender http response code, but at the end of the day we thought Page Visibility is the best way to solve this problem. We can talk about it some more. 17:17:35 plh2 has joined #webperf 17:18:41 Arvind: On the topic of discarding the page, there is value in discarding the page after some time as the page may be out of date. For example, the browser prerenders but the user doesn't click on the link for two hours. 17:22:28 Jatinder: Navigation Timing should have information on when the user switched to the prerendered page. Getting the delta of loadEventEnd and prerenderSwitch will give the perceived page load time (delta == loadEventEnd is normal page load, delta < loadEventEnd is perceived faster page load, delta >= loadEventEnd is instant page load). 17:24:51 Jatinder: We may also want to include information in Resource Timing for the page that initiated the prerender or prefetch. For example, any resource that was prefetch should be included in the Resource Timing with an initiator of "link:prefetch". Any page that was prerendered could be included as an entry similar to a subdocument with initiator type "link:prerender". 17:29:43 -Rob 17:35:47 - +1.408.203.aaee 17:36:06 plh3 has joined #webperf 17:36:13 Arvind: I'm not sure we should add this kind of information to the Timing API, because it's somewhat tangantial. 17:36:24 + +1.408.203.aagg 17:36:37 zakim, aagg is Arvind 17:36:37 +Arvind; got it 17:36:50 zakim, drop aaee 17:36:50 sorry, plh3, I do not see a party named 'aaee' 17:39:13 Jatinder: What about the case where the page is adding the link rel="prerender" dynamically after the page itself has loaded, so it doesn't impact the current page's performance. It might be useful for that page to know when the prerender occurs, especially if the browser delays the prerender. 17:39:55 Arvind: If the page is prerendering immediately, then there is no problem. If the prerender is delayed, we can consider adding a handler or a event that calls a callback to notify the page owner when the prerender occurs. 17:41:02 Ganesh: Are there statistics for link taken or not taken once it's prerendered? 17:42:36 Arvind: I know Google tracks some stats but not sure if they are published. For applications like search, people do click on it often. In other applications, it may not be as much. E.g., new stories that spans multiple pages the hit rate would be high. 17:43:04 Ganesh: I wonder if want to include in the spec if the click or not click count was given to the developer. 17:45:43 Jatinder: You can use the onclick event on the link. 17:47:27 Arvind: We can definitely include information on the benefits of prerender. 17:50:37 -ganesh 17:50:39 -Arvind 17:50:40 -Daniel 17:50:40 -[GVoice] 17:50:41 -[Microsoft] 17:50:41 -Plh 17:50:43 - +43.732.908.2aadd 17:50:44 RWC_web-per()1:00PM has ended 17:50:44 Attendees were +1.626.379.aaaa, [Microsoft], Plh, +1.720.746.aabb, Rob, Daniel, +1.650.701.aacc, +43.732.908.2aadd, Arvind, +1.408.203.aaee, [GVoice], +1.503.264.aaff, ganesh, 17:50:44 ... +1.408.203.aagg 19:46:30 Zakim has left #webperf 19:48:09 rrsagent, generate minutes 19:48:09 I have made the request to generate http://www.w3.org/2013/03/20-webperf-minutes.html plh 19:48:15 rrsagent, make logs public-visible