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

[minutes] 2012-03-07 Web Performance WG Teleconference #64

From: Jatinder Mann <jmann@microsoft.com>
Date: Wed, 7 Mar 2012 19:10:52 +0000
To: "public-web-perf@w3.org" <public-web-perf@w3.org>
Message-ID: <EE4C13A1D11CFA49A58343DE361B0B041723AD39@TK5EX14MBXC254.redmond.corp.microsoft.com>
Meeting Summary:



1.    Navigation Timing

The working group expects Navigation Timing to go to PR at the end of the month as WebIDL appears to be heading towards CR during that time period.



2.    Resource Timing

The working group reviewed all Last Call feedback. Most feedback has already been incorporated. The editors have decided to make two simple spec changes to make the spec more clear: the resource timing diagram will be updated to make the startTime behavior clear and the 'no exceptions' text will be updated to 'no additional exceptions'. Once the spec has been updated per feedback, there will remain no open issues on this spec. We expect this spec to move to CR phase thereafter.



3.    User Timing

The working group reviewed all Last Call feedback. The editors will update some text to make it more clear. Once the spec has been updated per feedback, there will remain no open issues on this spec. We expect this spec to move to CR phase thereafter.



4.    Performance Timeline

There is no open Last Call feedback issues on this spec. We expect this spec to move to CR phase.



5.    High Resolution Time

The specification has been updated per feedback from last week. The only remaining issue with this spec is a security review. IE, Chrome and W3C security mailing lists will be emailed about security questions. The working group has decided to take the security question as a Last Call feedback. The working group would like to move this spec to the Last Call phase for the standard Last Call time period.


Detailed Notes:



Web Perf Teleconference #64 3/07/2012



IRC log: http://www.w3.org/2012/03/07-webperf-irc


Meeting Minutes: http://www.w3.org/2012/03/07-webperf-minutes.html



Attendees

Present for Navigation Timing, Resource Timing and User Timing (4-5PM EST/1-2PM PST)

Jatinder Mann, James Simonsen, Luke Wagner, Zhiheng Wang


Present for Page Visibility, Efficient Script Yielding, Display Paint Notifications (4-5PM EST/2-3PM PST)

Meeting cancelled.



Scribe

Jatinder Mann



Contents

Agenda

1.     Review all Last Call feedback on Resource, User and Performance Timeline

2.     Discuss moving High Resolution Time to Last Call

--------------------------------------------------------------------------------
Navigation Timing

Jatinder: Per Philippe's comment, the LC period for WebIDL is over and the editor reports that he is optimistic in resolving the comments this week. As such, the webapps should be in a position to move it to CR within two weeks. That means that we could get a PR for nivagation timing for the end of the month.
Resource Timing

http://www.w3.org/2012/02/resource-timing-lc-issues.html

http://lists.w3.org/Archives/Public/public-web-perf/2011Sep/0009.html

The startTime attribute must return a DOMHighResTimeStamp with the time immediately before the user agent starts to queue the resource for fetching. If there are HTTP redirects or equivalent when fetching the resource and if all the redirects or equivalent are from the same origin as the current document, this attribute must return the same value as redirectStart. Otherwise, this attribute must return the same value as fetchStart.

Jatinder: Nic's question was about whether the current spec text was our intention?

James: Yes, it was.

Zhiheng: Agreed.

http://lists.w3.org/Archives/Public/public-web-perf/2011Oct/0042.html

James: Looks like we just want to make the diagram clearer.

Jatinder: Sounds good. Zhiheng, do you have the original powerpoint for the diagram?

Zhiheng: Yes, I will share.

http://lists.w3.org/Archives/Public/public-web-perf/2011Nov/0016.html

Jatinder: Per James Graham: Also, since the current wording evidently causes confusion.
... We currently say no exceptiuons.

James: We should say 'no additional exceptions'.

Jatinder: Once thes issues have been dealt with we will have responded to all last call issues.
User Timing

http://www.w3.org/2012/02/user-timing-lc-issues.html

https://dvcs.w3.org/hg/webperf/raw-file/d1498d8e0e5e/specs/UserTiming/Overview.html#privacy

James: His comments are fair, we should just update the wording.
Performance Timeline

Jatinder: There are no performance timeline last call issues.
... Once we have made the changes we discussed today, there will be no open last call issues on any of these specs. These specs can move to the CR phase.
High Resolution Time

Jatinder: I have responded to all feedbak to the spec. In particular, the text on subsequent deltas not being equal to zero has been is acceptable by the definition of monotonically increasing. Further, I have simplified the IDL definition.

James: We have one remaining question on the security issue. I have sent mail to our security team.

Jatinder: I will speak to Eric Lawrence on our end.

James: Let's also email the mailing list that Tony had emailed previously.

Jatinder: I recommend we take the security issue as a last call issue for this spec.
... Are we in favor of moving this spec to Last Call?

James: Yes, let's move it to last call and take the security question as a last call issue.

Ziheng: I am okay with Last Call.

Jatinder: Let's keep the standard time frame for last call.
Received on Wednesday, 7 March 2012 19:27:06 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 7 March 2012 19:27:06 GMT