15:58:20 RRSAgent has joined #webperf 15:58:20 logging to http://www.w3.org/2010/11/03-webperf-irc 15:59:31 scribe: AndersonQuach 15:59:41 meeting: Web Performance Working Group #08 16:00:11 agenda+Updates on Navigation Timing and Same-Origin 16:00:14 clear the agenda 16:00:17 list the agenda 16:00:22 agenda+ Updates on Navigation Timing and Same-Origin 16:00:28 agenda+ Updates on the timeline for Navigation Timing, From Working Draft to Recommendation 16:00:34 agenda+ Resource Timing and User Timing 16:00:39 agenda+ Any other business 16:00:42 save the agenda 16:00:47 present+ AndersonQuach 16:00:52 present+ NicJansma 16:01:21 RWC_web-per(WPWG)12:00PM has now started 16:01:28 +[Microsoft] 16:01:29 + +1.415.829.aaaa 16:01:44 chair: ArvindJain 16:02:07 rrsagent, set logs world-visible 16:02:09 + +1.415.568.aabb 16:02:11 NicJansma has joined #webperf 16:02:12 Christian has joined #webperf 16:03:21 + +1.650.214.aacc 16:03:36 present+ TonyG 16:03:39 present+ Christian 16:03:48 + +1.650.390.aadd 16:04:06 Zhiheng has joined #webperf 16:04:33 + +1.650.253.aaee 16:05:18 present+ ArvindJain 16:05:23 present+ JasonSobel 16:06:11 present+ Zhiheng 16:06:12 tonyg has joined #webperf 16:06:18 list the agenda 16:07:42 Zhiheng: Spec updated to include items discussed last conf call. 16:15:28 AndersonQuach: I see relaxed origin captured in the spec and HTML5, 5.3.1 same-origin restriction. 16:16:44 JasonSorbel: Yes, captured logon auth -> target page scenario well. 16:17:15 AndersonQuach: Yeah, right now navigationStart and redirectStart, redirectEnd is lost for landing page -> autho domain -> target domain. 16:17:36 NicJansma: how will this be decorated, previous page and current page must set a header or script value. 16:18:12 s/JasonSorbel/JasonSobel 16:18:29 JasonSobel: The group should follow-up with details offline perhaps. 16:19:03 NicJansma: This can be worked around now in JavaScript. 16:19:13 JasonSobel: This is nice to have and not critical. 16:19:26 JasonSobel: Hit small amount of people that can work around the issue. 16:19:55 Zhiheng: Let's follow-up offline. 16:21:40 TonyG: What is the status of CORS? Can we use this for solving this problem? 16:23:26 JasonSobel: Can we follow-up with the author annevk@opera.com with CORS and the status? 16:23:41 - +1.650.390.aadd 16:24:14 next agenda 16:24:22 topic: Updates on Navigation Timing and Same-Origin 16:25:23 sorry, got dropped call, dialing again. 16:25:40 JasonSobel: Let's check in with the timeline, let's understand where they are at before a go/no go with the usage of CORS. 16:25:57 TonyG: Last remaining question, when the timings are exposed. 16:26:15 TonyG: Make all the changes, to expose the key points. 16:26:18 + +1.650.390.aaff 16:27:33 Zhiheng: document.domain / relaxed origin, still want to specifiy host component and port number. We need to define clearly what we want. 16:27:45 Christian: why do we care about the port number? 16:28:57 NicJansma: W3C definition of origin is schema, host, and port. 16:31:07 Christian: I suggest same-origin policy to include document.domain. 16:31:39 http://msdn.microsoft.com/en-us/library/ms533028(VS.85).aspx 16:32:40 http://dev.w3.org/html5/spec/origin-0.html#relaxing-the-same-origin-restriction 16:33:08 Christian: At least in Firefox, document.domain is free, function to compare origin already takes it into account. 16:33:47 JasonSobel: same-origin policy captures the options, i. document.domain and ii. use of CORs and the timeline. 16:35:25 next topic 16:35:28 next agenda 16:35:39 topic: Updates on the timeline for Navigation Timing, From Working Draft to Recommendation 16:36:11 AndersonQuach: Target for 11/30/2010 for Last Call; and 01/07/2010 for Candidate Review 16:36:32 Zhiheng: Ideally we should have a Firefox reference implementation. Before last call. 16:36:51 Zhiheng: Targeting Last Call in Fb 16:39:09 JasonSobel: Don't understand why we have to delay for a 3rd reference implementation. If possible we should move faster. 16:39:31 Zhiheng: Firefox a significant part of the ua community. 16:40:13 Christian: Firefox wants the interface, currently not known who is working on it. 16:40:41 Christian: Could take up to Jan before it can be submitted to the Firefox feature repository. It could take a while before they are ready. 16:41:09 TonyG: Firefox, Jonas, Christian and Sergey have not raised problems with the spec. 16:44:32 AndersonQuach: To make progress we should target last call for end of Nov and target conformance tests and CR for Jan. 16:44:56 Zhiheng: Will follow-up Jonas on the timeline and Navigation Timing spec. 16:47:12 AndersonQuach: I can follow-up with submitting tests and hosting tests for Navigation Timing. 16:47:23 TonyG: I can contribute tests for conformance testing. 16:47:41 AndersonQuach: Great! IE has tests to contribute as well. 16:49:11 next agenda 16:49:22 topic: Resource Timing and User Timing 16:51:36 Zhiheng: can we access timing by ID or URL? 16:52:07 NicJansma: for URL can iterate over results in the interface. 16:53:11 NicJansma: Not everything have have an id and complications, change source image associated with id. we should have them individually captured. 16:53:53 Zhiheng: use case for resource id, or url, if there are many iframes and differentiate mine versus third party. 16:54:29 NicJansma: we see the limitations, similar API to get by id or url? 16:54:51 JasonSobel: the way people are going to use this is varied, allowing people to do filtering in script seems reasonable. 16:55:16 JasonSobel: don't mind to parse a blob to figure out what's interesting. 16:55:33 JasonSobel: i like that the developer does this in script. 16:58:31 JasonSobel: batched processing is the primary use. 16:59:01 JasonSobel: from onload indexed for a specific timing, is a nice to have. from facebook, the batched processing is what we already do. 17:03:42 TonyG: Let's get some ideas about the various scenarios and have the whole hour for it. 17:04:21 - +1.650.214.aacc 17:04:22 - +1.650.253.aaee 17:04:23 - +1.415.829.aaaa 17:04:26 -[Microsoft] 17:04:28 - +1.415.568.aabb 17:04:29 - +1.650.390.aaff 17:04:29 RWC_web-per(WPWG)12:00PM has ended 17:04:31 Attendees were [Microsoft], +1.415.829.aaaa, +1.415.568.aabb, +1.650.214.aacc, +1.650.390.aadd, +1.650.253.aaee, +1.650.390.aaff 17:12:55 regrets+ JasonWeber 17:36:18 mdelaney has joined #webperf 18:00:41 topic: Summary 18:05:27 1. The working group will discuss in mail the technical details of using document.domain in order to disclose navigationStart with respect to a relaxed same origin policy http://dev.w3.org/html5/spec/origin-0.html#relaxing-the-same-origin-restriction 18:05:42 2. JasonSobel will follow up with the author of CORS annevk@opera.com on the timeline of the working draft spec. 18:05:47 3. Zhiheng to follow-up with Jonas on Navigation Timing timeline and spec feedback. 18:06:05 4. Target Timeline for Navigation Timing, Last Call for 11/30/2010 and work towards Candidate Review for 1/15/2010. 18:06:10 5. Anderson to follow-up offline with conformance test infrastructure to host test cases. 18:06:14 6. The Web Performance working group to follow-up in mail to discuss the technical trade-offs of the Resource Timing proposals. 18:06:30 rrsagent, generate minutes 18:06:30 I have made the request to generate http://www.w3.org/2010/11/03-webperf-minutes.html AndersonQuach 18:06:48 rrsagent, set logs world-visible 18:37:29 mdelaney has joined #webperf 18:56:09 mdelaney_ has joined #webperf 18:59:39 dismiss Zakim 19:00:25 Zakim, please part 19:00:25 Zakim has left #webperf 19:00:29 rrsagent, please part 19:00:29 I see no action items