- From: Ilya Grigorik <igrigorik@google.com>
- Date: Tue, 14 Jul 2015 14:33:03 -0700
- To: public-web-perf <public-web-perf@w3.org>
- Message-ID: <CADXXVKozXsZKO92g-nbzwqZSWH0awY_YXCibhpMcUQaUL_JCxQ@mail.gmail.com>
Working Group Conference Call (3-4PM EST/12-1PM PST) Note that we'll be using new teleconf system. Dial-in details: https://www.w3.org/wiki/Web_Performance/Call_Information#VoIP ---- Tentative agenda: * requestIdleCallback feedback and next steps -- https://lists.w3.org/Archives/Public/public-web-perf/2015Jun/0126.html * SOP + Resource Timing + no-cors fetches -- https://github.com/w3c/resource-timing/issues/27 * Timing attacks (reopened) -- https://github.com/w3c/hr-time/issues/4 * Future of performance.timing and performance.navigation -- https://github.com/w3c/navigation-timing/issues/22 * PerformanceObserver needs target -- https://github.com/w3c/performance-timeline/pull/29#issuecomment-120996771 * dns-prefetch's future -- https://github.com/w3c/resource-hints/issues/37 * startTime/duration should be timestamps? -- https://github.com/w3c/performance-timeline/issues/31 * Recommended marks in user timing -- https://github.com/w3c/user-timing/issues/5 * Does Nav timing or Resource Timing get definition of requestStart correct? -- https://github.com/w3c/resource-timing/issues/25 Time permitting, triage other issues: http://w3c.github.io/webperf-dashboard/
Received on Tuesday, 14 July 2015 21:34:12 UTC