See also: IRC log
<trackbot> Date: 29 February 2012
trackbot, start telecon
<trackbot> Meeting: Web Performance Working Group Teleconference
<trackbot> Date: 29 February 2012
<dmandelin> I just dialed in too
<scribe> scribe: jatinder
<Alois> Dialed in
Jatinder: Was there any feedback to the spec?
<dmandelin> the users i talked to didn't seem to need to know the resolution, they just wanted to get the best resolution the system could provide
Tony: There was some feedback on the definition of the start of navigation. We should use navigationStart.
Jatinder: I agree that we should tie the definition in with navigationStart.
James: Regarding the minimum resolution, I think we should just leave it as a best effort.
<plh> I'm ok with best effort
Tony: I like it how it is.
... Boris had raised concerns on requestAnimationFrame?
Jatinder: I had responded on the thread. Seeing that developers were aware that they were using prefixed code that could still change behavior and requestAnimationFrame spec has only now just gone into Last Call, I don't think it's too late to make such changes.
Tony: What about performance.timing attributes?
Jatinder: They will remain as is. When using getEntries() you will get the new time.
Jatinder: http://www.w3.org/2012/02/resource-timing-lc-issues.html
http://lists.w3.org/Archives/Public/public-web-perf/2011Aug/0021.html
plh: Jatinder why don't you review the lists and get back to the mailing list if there are any issues.
Jatinder: Definitely.
Karen: What about mailing list discussions on iframe security?
Tony: We had closed that by saying we were going to use navigationStart.
Jatinder: I wrote a section on statistical fingerprinting. Seeing that cache hits and misses can be determined without sub-millisecond resolution.
James: We should continue the discussion with our security folks and close on this.
close action-88
<trackbot> ACTION-88 Respond to Anne's comment on privacy section for Page Visibility closed
closs action-69
close action-69
<trackbot> ACTION-69 Create High Resolution Time specification closed
close action-6
<trackbot> ACTION-6 Investigate https://w3c-test.org/ closed
close action-63
<trackbot> ACTION-63 Inherited objects should return sub-millisecond resolution closed
close action-71
<trackbot> ACTION-71 Propose use cases for an Instrumentation/Timing API to be used for tooling purposes closed
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) No ScribeNick specified. Guessing ScribeNick: JatinderMann Found Scribe: jatinder Default Present: pchampin, Plh, [Microsoft], Luke, +1.510.333.aaaa, +43.732.908.2aabb, +1.404.978.aacc, Tony Present: pchampin Plh [Microsoft] Luke +1.510.333.aaaa +43.732.908.2aabb +1.404.978.aacc Tony plh simonjam alois dmandelin karen tonyg WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Found Date: 29 Feb 2012 Guessing minutes URL: http://www.w3.org/2012/02/29-webperf-minutes.html People with action items: WARNING: Input appears to use implicit continuation lines. You may need the "-implicitContinuations" option.[End of scribe.perl diagnostic output]