- From: Pete Snyder <psnyder@brave.com>
- Date: Wed, 4 Dec 2019 11:49:14 -0800
- To: Xiaoqian Wu <xiaoqian@w3.org>
- Cc: public-privacy <public-privacy@w3.org>, yoav@yoav.ws
We did a privacy review and the results were not welcomed by the WG and the issue was decided by the director. Is this a request for _another_ full privacy review, or a new review for issues district from the previously discussed one? > On Dec 4, 2019, at 3:56 AM, Xiaoqian Wu <xiaoqian@w3.org> wrote: > > Hi PING, > > The WebPerf WG is preparing to move the Resource Timing Level 2 spec to CR, > https://www.w3.org/TR/performance-timeline-2/ > > This spec defines a PerformanceResourceTiming interface, which participates in the Performance Timeline and facilitates timing measurement of downloadable resources. The information exposed by this interface is defined by a set of attributes[1] in the PerformanceResourceTiming interface. > > For Cross-origin Resources, the spec defines a Timing-Allow-Origin Response Header[2] and a timing allow check algorithm to determine whether their information can be fully exposed. Please also look at the Privacy and Security section[3] for more detail. > > Please let us know if there is any privacy concern for Performance Timeline before the end of January, either by email <public-web-perf@w3.org> or use GitHub issues <https://github.com/w3c/resource-timing>. > > Thanks. > > -xiaoqian > > [1] https://www.w3.org/TR/resource-timing-2/#sec-performanceresourcetiming > [2] https://www.w3.org/TR/resource-timing-2/#dfn-timing-allow-check > [3] https://www.w3.org/TR/resource-timing-2/#sec-privacy-security > >
Received on Wednesday, 4 December 2019 19:49:20 UTC