<trackbot> Date: 24 August 2011

<scribe> scribe: JatinderMann

1. Discuss microsecond timestamp resolution.

Jatinder: The problem is we may want to provide sub-millisecond resolution for scenarios where microsecond solution is wanted, like graphics frame rate calculation. Microsecond resolution may not be necessary be for Navigation or Resource Timing, but may be needed for User and future timings like Graphics.

JamesS: Based on the mailing list conversation, seeing that we have a monotonic clock, people shouldn't be comparing with Date.now(), so I think that argument shouldn't be used.

Jatinder: Yes, that is a good point. The two shouldn't be compared based on that reason.

Nic: But we have shipped Navigation Timing? We wouldn't want to break compatibility if we change the offset?

JamesS: We can report microsecond resolution without the unix epoch offset when using getEntries() method but return the current millisecond unix epoch offset when looking at performance.timing directly.

Nic: That is a potential compromise.

Zhiheng: Do we need microsecond resolution for Navigation or Resource Timing?

JamesS: We could spec it out that the NT or RT can round up to millisecond resolution if the UA wants.

Zhiheng: Makes sense.

Nic: So long long or double?

JamesS: We should stick with double and not deal with this problem again.

Jatinder: And the double would be offset from the navigationStart from root document?

JamesS: Correct.
... We should probably also change the Monotonic Clock to not use unix epoch.
... We still need to respond to the finger printing email.

Tony: What was our planned response? Is it that there is no privacy concern or that the privacy concern isn't any worse then it is today?

Nic: To paraphrase, our findings were that the privacy concern wasn't any worse then it is today with what you can do with the onload events.

Jatinder: We should take an action to both respond to that email thread with our findings.

This is scribe.perl Revision: 1.136  of Date: 2011/05/12 12:01:43  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Found Scribe: JatinderMann
Inferring ScribeNick: JatinderMann
Default Present: [Microsoft], +1.650.214.aaaa, Arvind
Present: [Microsoft] +1.650.214.aaaa Arvind Jatinder Tony JamesS Nic Karen Zhiheng

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Found Date: 24 Aug 2011
Guessing minutes URL: http://www.w3.org/2011/08/24-webperf-minutes.html
People with action items: