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

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

From: Ilya Grigorik <igrigorik@gmail.com>
Date: Tue, 31 May 2016 13:14:41 -0700
Message-ID: <CAKRe7JFX7yij9r5f2Ff2-XWuEH5jOiqUX5ByPZTte1EbJS7DuQ@mail.gmail.com>
To: "public-webappsec@w3.org" <public-webappsec@w3.org>
Cc: Todd Reifsteck <toddreif@microsoft.com>, Philippe Le H├ęgaret <plh@w3.org>
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
>
Received on Tuesday, 31 May 2016 20:15:48 UTC

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