- From: Ilya Grigorik <igrigorik@google.com>
- Date: Tue, 25 Aug 2015 15:53:40 -0700
- To: public-web-perf <public-web-perf@w3.org>
- Message-ID: <CADXXVKpq+XRnYbHZLxu+G73FpiWTc=e4fV7tw2t209YMFYQFNA@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 ---- Agenda: * Next steps with Animation Timing spec [1] * Publish requestIdleCallback FPWD * Updated obsoleted EDs with links to latest drafts? [2] * PerformanceTiming#dom* attributes are poorly defined [3] * Should Frame Timing report slow frames only? [4] * Use Timing-Allow-Origin to determine same-origin on redirects? [5] * PerfTimeline task queue must be processed at least once every Xms? [6] * requestStart definition differ with navtimg [7] Time permitting, triage other issues on: http://w3c.github.io/webperf-dashboard/ [1] https://lists.w3.org/Archives/Public/public-web-perf/2015Aug/0005.html [2] https://lists.w3.org/Archives/Public/public-web-perf/2015Aug/0014.html [3] https://lists.w3.org/Archives/Public/public-web-perf/2015Aug/0013.html [4] https://github.com/w3c/frame-timing/issues/47 [5] https://github.com/w3c/navigation-timing/issues/20 [6] https://w3c.github.io/performance-timeline/#performance-timeline [7] https://github.com/w3c/resource-timing/issues/25
Received on Tuesday, 25 August 2015 22:54:47 UTC