- From: Gilles Dubuc <gilles@wikimedia.org>
- Date: Tue, 18 Dec 2018 10:15:14 +0100
- To: Yoav Weiss <yoav@yoav.ws>
- Cc: public-web-perf <public-web-perf@w3.org>
- Message-ID: <CALac36WcraU_e0ks3D_oJ70fgBnY3aL0OqtK1F+1Ef=WDPvJqw@mail.gmail.com>
Was the date of the call announced earlier elsewhere? I missed it because there was only 24 hours notice from that email and I saw it too late. On Wed, Dec 12, 2018 at 2:44 PM Yoav Weiss <yoav@yoav.ws> wrote: > Heya folks! > > Please join us on the call this Thursday. I plan to discuss the missing > pieces in getting us to ship long-standing specs, but feel free to add > things you want to discuss to the agenda > <https://docs.google.com/document/d/10dz_7QM5XCNsGeI63R864lF9gFqlqQD37B4q8Q46LMM/edit?pli=1#heading=h.ohc3prc50j0w> > . > > > - > > Resource Timing > - > > should redirected navigations have a workerStart value if a > previous redirect URL was intercepted > <https://github.com/w3c/resource-timing/issues/118> > - > > spec what requestStart, responseStart, and responseEnd should > represent when service worker is involved > <https://github.com/w3c/resource-timing/issues/119> > - > > Many of the tests are flaky > <https://github.com/w3c/resource-timing/issues/182> > - > > Add a note regarding negative timestamps for navigation preload > requests <https://github.com/w3c/resource-timing/pull/183> > - > > User Timing > - > > What’s blocking shipping? (WPT results > <https://wpt.fyi/results/user-timing?label=experimental>) > - > > Navigation Timing > - > > WPT results > <https://wpt.fyi/results/navigation-timing?label=experimental> > > > Cheers :) >
Received on Tuesday, 18 December 2018 09:15:54 UTC