W3C home > Mailing lists > Public > public-webappsec@w3.org > May 2016

Re: [review] Performance API's, Security and Privacy

From: Wendy Seltzer <wseltzer@w3.org>
Date: Tue, 31 May 2016 17:40:12 -0400
To: Ilya Grigorik <igrigorik@gmail.com>, "public-webappsec@w3.org" <public-webappsec@w3.org>
Cc: Todd Reifsteck <toddreif@microsoft.com>, Philippe Le H├ęgaret <plh@w3.org>
Message-ID: <574E04BC.9070308@w3.org>
Thanks for the ping. I opened a couple issues and an editorial PR.

--Wendy

On 05/31/2016 04:14 PM, Ilya Grigorik wrote:
> Forgot to mention. If you have any feedback, or spot any issues, please
> open an issue on GitHub:
> https://github.com/w3c/perf-security-privacy/issues
> 
> thanks!
> 
> *p.s. fixed a bunch of grammar and spelling issues -- thanks for catching
> those!*
> 
> On Wed, May 25, 2016 at 10:36 AM, Ilya Grigorik <igrigorik@gmail.com> wrote:
> 
>> Hey all.
>>
>> Would love to hear any thoughts or comments on a note we've been working
>> on over at webperf (for motivation, see [1]):
>>
>> "The fact that something is possible to measure, and may even be highly
>> desirable and useful to expose to developers, does not meant that it can be
>> exposed as runtime JavaScript API in the browser, due to various privacy
>> and security constraints. The goal of this document is to explain why that
>> is the case, and to provide guidance for what needs to be considered when
>> making or evaluating a proposal for such APIs."
>>
>> https://w3c.github.io/perf-security-privacy/
>>
>> ig
>>
>> [1] https://lists.w3.org/Archives/Public/public-web-perf/2016Apr/0010.html
>>
> 


-- 
Wendy Seltzer -- wseltzer@w3.org +1.617.715.4883 (office)
Policy Counsel and Domain Lead, World Wide Web Consortium (W3C)
https://wendy.seltzer.org/        +1.617.863.0613 (mobile)
Received on Tuesday, 31 May 2016 21:40:16 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:54:56 UTC