W3C home > Mailing lists > Public > public-privacy@w3.org > April to June 2016

[review] Performance APIs, Security and Privacy

From: Ilya Grigorik <ilya@igvita.com>
Date: Wed, 1 Jun 2016 14:10:29 -0700
Message-ID: <CAKRe7JEaokQd8Vmz_b=LsVmz0nigKPxJMiZa7vS0J8=NwWHp9A@mail.gmail.com>
To: public-privacy@w3.org
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 mean 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/

If you have any feedback, or spot any issues, please open an issue on
GitHub:
https://github.com/w3c/perf-security-privacy/issues

Thanks!
ig

[1] https://lists.w3.org/Archives/Public/public-web-perf/2016Apr/0010.html
Received on Wednesday, 1 June 2016 21:11:38 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:49:33 UTC