W3C home > Mailing lists > Public > public-web-perf@w3.org > February 2017

Re: [2/8/17] webperf group call @ 10AM PST

From: Shubhie Panicker <panicker@google.com>
Date: Tue, 7 Feb 2017 19:48:14 -0800
Message-ID: <CAK7ODi8qRujC-7b=reZDGs3TsLuy8vH+z-XMWbqr_zpP5JogQA@mail.gmail.com>
To: Ilya Grigorik <igrigorik@google.com>
Cc: public-web-perf <public-web-perf@w3.org>
Adding one more (time permitting):
https://github.com/w3c/user-timing/issues/24


On Tue, Feb 7, 2017 at 5:59 PM, Ilya Grigorik <igrigorik@google.com> wrote:

> Hangout: https://hangouts.google.com/hangouts/_/chromium.org/webperf-wg
>
> --- Agenda:
>
>    - *Performance Timeline*
>       - Performance.timing shouldn't be deprecated
>       <https://github.com/w3c/performance-timeline/issues/68>
>       - Clarify disconnecting a PerformanceObserver that has observed
>       entries <https://github.com/w3c/performance-timeline/issues/66>
>       - Clarify sort order for entries with equivalent startTime
>       <https://github.com/w3c/performance-timeline/issues/67>
>       - Clarify how PerformanceObserver invokes the callback
>       <https://github.com/w3c/performance-timeline/issues/65>
>
>
>    - *Resource Timing*
>       - Clarify whether UA can clear the buffer under memory pressure
>       <https://github.com/w3c/resource-timing/issues/94>
>       - Increase limit of 150 for PerformanceEntrys?
>       <https://github.com/w3c/resource-timing/issues/89>
>
>       - Long Tasks, Paint Timing: do we need to update WG charter?
>    - Long Tasks / Paint API v1 progress updates
>    - Beacon: test + Fetch integration updates
>
>
>
>
Received on Wednesday, 8 February 2017 03:48:57 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 February 2017 03:48:57 UTC