W3C home > Mailing lists > Public > public-web-perf@w3.org > March 2012

[UserTiming] Privacy Section

From: Jatinder Mann <jmann@microsoft.com>
Date: Thu, 8 Mar 2012 04:56:11 +0000
To: "public-web-perf@w3.org" <public-web-perf@w3.org>
Message-ID: <EE4C13A1D11CFA49A58343DE361B0B041723B8AB@TK5EX14MBXC254.redmond.corp.microsoft.com>
I am in the process of rewording the current User Timing privacy section, http://dvcs.w3.org/hg/webperf/raw-file/tip/specs/UserTiming/Overview.html#privacy, to use the same origin syntax and extend the definition to PerformanceMark and PerformanceMeasure interfaces. The current privacy section is pasted below:

"UserTiming potentially exposes information about specific activities on a page. This information must explicitly not be accessible in cross-domain situations and made available to only the server where the root document originates."

This text suggests that the getMarks and getMeasures functions will return empty Arrays when invoked from scripts originating from different origins and the PerformanceMark and PerformanceMeasure interfaces will zero out data for the startTime and duration attributes when invoked from scripts originating from different origins. As the default behavior, it makes sense from a privacy point of view to do this.

Do we want to allow sites to be able to allow cross-origin scripts from accessing this information using a CORS-like HTTP response header, as we did for Resource Timing? You can imagine a situation where a site has instrumented their scripts with marks and measures, but has contracted out the work to do the reporting to a third-party.


Received on Thursday, 8 March 2012 04:56:45 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:01:11 UTC