- From: Ilya Grigorik <igrigorik@google.com>
- Date: Wed, 18 Jan 2017 01:43:56 +0100
- To: public-web-perf <public-web-perf@w3.org>
- Message-ID: <CADXXVKqT2HhjFy_OrQjTUEhbz04tjaH0vQ4kffzkq5BoEEG_Xg@mail.gmail.com>
Hangout: https://hangouts.google.com/hangouts/_/chromium.org/webperf-wg --- Agenda: - *Nav Timing L2* - Report URL in "name" attribute instead of "document"? <https://github.com/w3c/navigation-timing/issues/59> - Data bias issues due to deferring reporting of all nav timing metrics to the load event <https://github.com/w3c/navigation-timing/issues/50#issuecomment-268919388> - *Performance Timeline * - L2: Lack of feature detection option for new entry types <https://github.com/w3c/performance-timeline/issues/64> - L3: Ability to observe past set of performance entries <https://github.com/w3c/performance-timeline/issues/56#issuecomment-268922807> - Long Tasks V1 progress updates - FP & FCP data analysis results <https://docs.google.com/document/d/1XVP9jaZT7acQtK5O6vO-mIz31i5iB-pZn1S41_YP6p0/edit#> comparing paint time with subsequent timestamps - *Resource Timing L1 * - From PR request review: "It appears that Timing-Allow-Origin was not tested. I think the implementation report is incomplete without tests for that feature." - requestIdleCallback L1 CR <https://github.com/w3c/requestidlecallback/issues/48> check-in..
Received on Wednesday, 18 January 2017 00:45:15 UTC