See also: IRC log
<trackbot> Date: 13 June 2012
<plh> http://lists.w3.org/Archives/Public/public-web-perf/2012May/0100.html
https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/NavigationTiming2/Overview.html
<plh> http://www.w3.org/wiki/Web_Performance/Publications
<plh> action-73?
<trackbot> ACTION-73 -- Jason Weber to propose ideas on improving sending data prior to unload -- due 2012-02-29 -- OPEN
<trackbot> http://www.w3.org/2010/webperf/track/actions/73
<plh> action-70?
<trackbot> ACTION-70 -- Jatinder Mann to share proposed Background Activity specification -- due 2012-02-29 -- OPEN
<trackbot> http://www.w3.org/2010/webperf/track/actions/70
<plh> action-97?
<trackbot> ACTION-97 -- Tony Gentilcore to check with Adam Barth on Memory Leak API -- due 2012-04-11 -- OPEN
<trackbot> http://www.w3.org/2010/webperf/track/actions/97
<plh> action-98?
<trackbot> ACTION-98 -- Alois Reitbauer to come up with bandwidth use cases and API -- due 2012-04-11 -- OPEN
<trackbot> http://www.w3.org/2010/webperf/track/actions/98
Jatinder: Sigbjorn raised
concerns about moving this spec to PR if we intend to replace
this API with the one definednnIn Navigation Timing 2.
... After some discussions about the timebase of
DOMHighResTimeStamp and comparing performance.now()n values
across, it was clear that in order to (A) measure
performance.now() from the navigation start of a document, we
need to define, at least internally, a
performance.timing.navigationStart value, (B) in order to
compare performance.now() values across frames, we need to be
able to add performance.timing.navigationStart to
performance.now() t
... Aside from our other arguments for standardizing Navigation
Timing and working on the next version of the spec, I think
these are clear use cases where we need to have Navigation
Timing standardized and implemented interoperably in order to
use High Resolution Time. What are your thoughts Philippe?n
Philippe: If we believe there is value in UA to implement Navigation Timing, then we should standarize it. Do we believe UAs should implement Navigation Timing?
Jatinder: Yes.
Arvind: Yes.
Philippe: I will respond to Sigbjorn on the mailing list. We should plan to move Navigation Timing to PR in the next two weeks and move Navigation Timing 2 to FPWD.
Philippe: Any updates from Resource Timing?
Jatinder: I have action items to
update the initiatorType definition to be tied to the element's
localname and the object's constructor. This doesn't change the
behavior, just implementation. I will update the spec.
... Also, we wanted to include a short processing model for
Timing-Allow-Origin that clarifies the behavior. There is no
real change of behavior here as well.
Philippe: Updates on User Timing?
Jatinder: There are three
changes: getMarks(), getMeasures() should return an object,
example needs fixing and I need to add details in the privacy
section to clarify the current behavior.
... These are the only feedback we got during Last Call. I am
working on making those changes.
Philippe: Once these changes are made, we should be able to move this spec forward to CR.
Philippe: Any Last Call feedback on Performance Timeline?
Jatinder: Just an update to the example.
Philippe: We should be able to move that one to CR along with the others once those changes have been made.
Philippe: Any feedback?
Jatinder: There was a discussion on the timebase for HRT. However, it has been resolved with the current behavior remaining.
Philippe: Page Visibility feedback?
Jatinder: There is Issue-8 that has been agreed upon now. I am working on updating the spec. I raised a concern on creating iframe specific behavior, we had agree to tie everything to top level browsing context.
Arvind: I will follow up with the Chrome team to see their opinion here.
Jatinder: I will start making the rest of that change. This is the last remaining item on this spec. Once this has been closed, we should discuss moving this spec forward.
Philippe: Can we ready this spec fo FPWD in the next two weeks?
Jatinder: Yes, that should be
fine.
... There was an issue brought up on the mailing list about
IE9's support of window.performance.toJSON and how that isn't
spec'd out. Should we consider adding that behavior to
Navigation Timing 2? Considering we expect most users to
stringify this data and send to a server, seems like a logical
choice.
Arvind: I will follow up with the Chrome team to get their opinion and get back.
Philippe: I will follow up with the editors to see if they are working on making updates.
Philippe: Our charter expires at the end of this month. We need to either ask for an extension of this charter or propose a new charter. In order to work on new things, we will need a new charter. We have a couple of action items on folks to research new ideas; these will need a charter update. Per Jason Weber though, he wanted to first complete these specs before starting work on others.
Jatinder: Considering we are very near done with these specs, I would also prefer focussing on these spec and finishing them up before moving to the next ones.
Arvind: I believe HARS should be covered in the current charter anyway.
Philippe: I will follow up on getting the charter extended.
trackbot, generate minutes
<trackbot> Sorry, JatinderMann, I don't understand 'trackbot, generate minutes'. Please refer to http://www.w3.org/2005/06/tracker/irc for help
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 Inferring Scribes: JatinderMann Default Present: +43.664.853.aaaa, +1.408.203.aabb, [Microsoft], +1.408.203.aacc, Plh, Alois, Arvind Present: +43.664.853.aaaa +1.408.203.aabb [Microsoft] +1.408.203.aacc Plh Alois Arvind WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Found Date: 13 Jun 2012 Guessing minutes URL: http://www.w3.org/2012/06/13-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]