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

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

From: Ilya Grigorik <igrigorik@google.com>
Date: Tue, 7 Feb 2017 17:59:47 -0800
Message-ID: <CADXXVKpfvTz3pc=rTmGK41qeZt1hCpO173_pE7KG5Qyiz=k94A@mail.gmail.com>
To: public-web-perf <public-web-perf@w3.org>
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 02:01:18 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 February 2017 02:01:19 UTC