- From: Philippe Le Hegaret <plh@w3.org>
- Date: Thu, 21 Apr 2016 10:25:17 -0400
- To: Ilya Grigorik <igrigorik@google.com>, public-web-perf <public-web-perf@w3.org>
On 04/19/2016 07:52 PM, Ilya Grigorik wrote: > *** note: this week's call is moved to Thursday *** > > Dial-in details: > https://www.w3.org/wiki/Web_Performance/Call_Information#VoIP > > Tentative agenda: > > * PerfObserver TAG feedback > o https://github.com/w3ctag/spec-reviews/issues/18#issuecomment-203969203 > o https://github.com/w3c/performance-timeline/pull/52 > * Nav + Resource Timing tests > o https://github.com/w3c/resource-timing/issues/46 > o https://github.com/w3c/navigation-timing/issues/39 > * Page Visibility > o Define onvisibilitychange: > https://github.com/w3c/page-visibility/pull/23 > o Tests for visibilitychange: > https://github.com/w3c/page-visibility/issues/21 > * Land continuous IDL updates? > o https://github.com/w3c/resource-timing/pull/51 > o https://github.com/w3c/navigation-timing/pull/41 > * Beacon > o Add method to sendBeacon: https://github.com/w3c/beacon/pull/27 > * requestIdleCallback > o Integration with Intersection & PerfObserver? * draft charter https://w3c.github.io/charter-webperf/ One thing we should consider is whether we should push some of our documents into WICG instead, eg Server Timing. Philippe
Received on Thursday, 21 April 2016 14:25:20 UTC