19:57:04 RRSAgent has joined #webperf 19:57:04 logging to http://www.w3.org/2011/10/19-webperf-irc 19:57:16 trackbot-ng, start telcon 19:57:18 RRSAgent, make logs world 19:57:20 Zakim, this will be WPWG 19:57:21 ok, trackbot; I see RWC_web-per(WPWG)4:00PM scheduled to start in 3 minutes 19:57:21 Meeting: Web Performance Working Group Teleconference 19:57:22 Date: 19 October 2011 19:58:23 JatinderMann has joined #webperf 19:58:32 trackbot, start teleconf 19:58:35 RRSAgent, make logs world 19:58:37 Zakim, this will be WPWG 19:58:37 ok, trackbot; I see RWC_web-per(WPWG)4:00PM scheduled to start in 2 minutes 19:58:38 Meeting: Web Performance Working Group Teleconference 19:58:38 Date: 19 October 2011 19:59:37 RWC_web-per(WPWG)4:00PM has now started 19:59:37 +Plh 20:01:32 + +1.650.253.aaaa 20:01:33 - +1.650.253.aaaa 20:01:33 + +1.650.253.aaaa 20:01:51 + +43.664.853.aabb 20:01:52 +[Microsoft] 20:02:21 Alois has joined #webperf 20:02:32 simonjam has joined #webperf 20:02:32 present+ Jatinder 20:02:36 present+ Arvind 20:02:41 present+ Alois 20:02:46 present+ Philippe 20:03:07 + +1.650.214.aacc 20:03:28 present+ JamesS 20:03:44 + +44.207.881.aadd 20:04:07 present+ TonyG 20:04:28 +??P5 20:04:40 Arvind: FYI, Andriod has started to implement NavigationTiming. 20:05:19 Jatinder: IE9 on Mango also supports Navigation Timing. 20:07:55 Topic: Timing Spec Updates 20:08:28 Jatinder: I have gone ahead and made spec updates to comply with ACTION-52, 53, and 54. Please go ahead and review the changes. 20:09:12 ... I have also updated test_timing_xserver_redirect.html to change the document.location.host to documentation.location.hostname. This fixes the issues on all browsers. Please do review. 20:09:37 Topic: Resource Timing Security/Privacy Review 20:10:43 Tony: The discussion with the public-web-security mailing list is given here: http://lists.w3.org/Archives/Public/public-web-security/2011Oct/0019.html 20:17:55 Jatinder: Based on cache hits and misses, malicious entities can determine with strong certainty when a resource is from a third party site. Based on our currenty third party restrictions, we don't give any additional information than what can already be determined today. 20:19:50 zhihengw has joined #webperf 20:20:59 Tony: The mailing list brought up concerns about XSS. Though, once you have XSS on your page, all bets are off. 20:21:46 Jatinder: IE9 has a XSS filter that blocks XSS on sites. Other UAs may have this, which will mitigate this concern. 20:22:08 Jatinder: What about the opt-out option mentioned in the mailing list? Is this something we should consider? 20:33:42 "User agents must not send location information to Web sites without the express permission of the user." 20:33:46 http://www.w3.org/TR/geolocation-API/#security 20:34:16 James: If we are to draw a line on the opt-out option, we should let user's opt-out of all of web timing, not just the third party restrictions. 20:37:24 Karen: I would prefer if we allowed user's to just turn on the third-party restrictions, not all of web timing. 20:37:44 Zhiheng: I agree to not allow turn off all web timings. 20:50:19 - +1.650.214.aacc 20:50:20 -Plh 20:50:20 - +1.650.253.aaaa 20:50:21 - +44.207.881.aadd 20:50:21 -[Microsoft] 20:50:23 -??P5 20:50:28 - +43.664.853.aabb 20:50:29 RWC_web-per(WPWG)4:00PM has ended 20:50:31 Attendees were Plh, +1.650.253.aaaa, +43.664.853.aabb, [Microsoft], +1.650.214.aacc, +44.207.881.aadd 20:59:20 RWC_web-per(WPWG)4:00PM has now started 20:59:21 +Plh 20:59:30 Jatinder: Considering when you visit a site that site already has this information. That site can sell this information to third-parties. To mitigate such a risk, sites use a privacy policy to tell users they aren't selling this information. Seems like when a site uses the http header to give this information to third parties is not much different. Privacy policies should stop sites from using the header. I don't think there is a difference. 20:59:37 Arvind: I think we all agree to keep the spec as is. 20:59:58 Tony: The spec should include this discussion and our mitigation to make this clear to readers. 21:00:11 ACTION Jatinder to update Resource Timing security/privacy section. 21:00:11 Created ACTION-55 - Update Resource Timing security/privacy section. [on Jatinder Mann - due 2011-10-26]. 21:00:21 Zhihend: Per my action item, looks like the HTML5 references are good. But I am still in process of finishing this. 21:00:42 Jatinder: We should target to have this data for TPAC. That will be a good data point in this discussion. 21:00:51 present+ Karen 21:01:35 +[Microsoft] 21:03:22 Plh: There are two tests that Firefox is failing on. We should figure out whether there is a test case bug or if it is a Firefox bug. 21:03:40 Karen: Yes, I was hoping we can discuss. Boris and I have a discussion on the mailing list. 21:04:54 Karen: We may want to re-evaluate the header. I will follow up with the IE Security team. 21:05:05 Topic: Page Visibility Test Cases and Specs 21:06:28 + +1.650.253.aaaa 21:11:23 Jatinder: With the spec updates I've made, we have closed on many of the spec questions Boris brought up. The remaining issue was whether Page Visibilty should change state on navigate away. 21:11:41 Arvind: I think the spec should be updated to make it clear that on navigate away, Visibility shouldn't be changed. 21:13:56 Karen: Also, in the unload cancel case, the Visibility may be hidden for a moment, even though the Page has always been visible. 21:19:55 Jatinder: I will see if we can update the spec to make this point clear. 21:21:06 Jatinder: Please review the Page Visibility test cases. Once we are happy with the changes, I can move the tests to the approved directory. 21:21:22 ... Also, should we keep the prefixes in the test cases or test what the spec says? 21:21:41 plh: We can keep the prefixes in the test cases for now. When we go to CR, we need to remove them so we are testing the spec. 21:21:45 Jatinder: Agreed. 21:23:59 -Plh 21:24:00 - +1.650.253.aaaa 21:24:00 -[Microsoft] 21:24:01 RWC_web-per(WPWG)4:00PM has ended 21:24:03 Attendees were Plh, [Microsoft], +1.650.253.aaaa 21:25:55 Karen: When you go to http://w3c-test.org/webperf/tests/approved/navigation-timing/html5/test_document_open.html, I get a 404 message stating "timing/resources/blank_page_yellow.htm was not found on this server." 21:26:10 rrsagent, generate minutes 21:26:10 I have made the request to generate http://www.w3.org/2011/10/19-webperf-minutes.html JatinderMann 21:37:30 rrsagent, generate minutes 21:37:30 I have made the request to generate http://www.w3.org/2011/10/19-webperf-minutes.html JatinderMann