- From: Philippe Le Hegaret <plh@w3.org>
- Date: Wed, 4 May 2016 11:20:46 -0400
- To: Ilya Grigorik <igrigorik@google.com>, public-web-perf <public-web-perf@w3.org>
On 05/03/2016 12:32 PM, Ilya Grigorik wrote:
> Dial-in details:
> https://www.w3.org/wiki/Web_Performance/Call_Information#VoIP
>
> Agenda:
>
> * Charter updates
> * Next steps for Resource Timing L1
> o https://lists.w3.org/Archives/Public/public-web-perf/2016Apr/0003.html
Here is what I think we should do:
1. Make sure we looked at
https://w3ctag.github.io/security-questionnaire/
and have answers in the spec for all of the relevant questions.
2. Get a review or an ack from webappsec
3. Transition to CR
> * "local" vs "remote" performance API's: privacy, security, best practices
> o https://lists.w3.org/Archives/Public/public-web-perf/2016Apr/0010.html
>
> Issues:
>
> * [resource-timing] Distinguish "Not-Allowed" from zero value entries
> o https://github.com/w3c/resource-timing/issues/42
> * [navigation-timing] Relationship between
> performance.timing.navigationStart and hr-time time origin
> o https://github.com/w3c/navigation-timing/issues/43
> * [beacon] Allow setting HTTP(S) headers in beacon
> o https://github.com/w3c/beacon/issues/30
> * [requestIdleCallback] land tests?
> o https://github.com/w3c/web-platform-tests/pull/2163
* Next step for Page Visibility 2?
* Next Charter
Current proposal is to:
* keep Preload, Resource Hints, and rIC as part of the webperf group
* move Server Timing, Frame Timing, and Reporting + NEL to WICG
Philippe
Received on Wednesday, 4 May 2016 15:20:49 UTC