RE: Resource Timing and User Timing issues list

The editors have reviewed and responded to all Resource Timing Last Call issues listed in http://www.w3.org/2012/02/resource-timing-lc-issues.html. I have summarized the issue resolution below:

Issue: Misc edits - http://lists.w3.org/Archives/Public/public-web-perf/2011Aug/0021.html 
Considering we want to call out that duration returns a DOMHighResTimeStamp, the current text is more clear. No change to be made here.

Issue: CORS - http://lists.w3.org/Archives/Public/public-web-perf/2011Sep/0001.html 
As startTime and responseEnd are never zero’d out, you will always get third party durations, but not specific timestamps. Zhiheng had made changes to the processing model to this effect two weeks ago. This issue is closed.

Issue: startTime and fetchStart - http://lists.w3.org/Archives/Public/public-web-perf/2011Sep/0009.html 
This issue has been closed, as the spec text matches our intentions. Please see the mailing list discussion: http://lists.w3.org/Archives/Public/public-web-perf/2012Mar/0006.html. 

Issue: startTime - http://lists.w3.org/Archives/Public/public-web-perf/2011Oct/0042.html 
The editors have agreed to update the diagram to make the startTime behavior more clear. Please see this thread: http://lists.w3.org/Archives/Public/public-web-perf/2012Mar/0008.html. 

Issue: Exceptions - http://lists.w3.org/Archives/Public/public-web-perf/2011Nov/0008.html 
The spec text has been updated from ‘no exceptions’ text to ‘no additional exceptions’. Please see this thread: http://lists.w3.org/Archives/Public/public-web-perf/2012Mar/0009.html. 

Issue: Misc: http://lists.w3.org/Archives/Public/public-web-perf/2011Nov/0008.html 
All of Sigbjorn’s feedback on typos and text has already been incorporated. Please see this thread: http://lists.w3.org/Archives/Public/public-web-perf/2012Mar/0010.html 

Issue: Opt in vs Opt Out and initiatorType attributes - http://lists.w3.org/Archives/Public/public-web-perf/2012Jan/0011.html   
There are no actions on the spec here. I have responded in this thread: http://lists.w3.org/Archives/Public/public-web-perf/2012Mar/0011.html 

With these changes, there are no remaining Last Call feedback to address. 

Thanks,
Jatinder

-----Original Message-----
From: Philippe Le Hegaret [mailto:plh@w3.org] 
Sent: Tuesday, February 28, 2012 5:28 PM
To: public-web-perf
Subject: Resource Timing and User Timing issues list

I created issues list for Resource Timing:
 http://www.w3.org/2012/02/resource-timing-lc-issues.html


and for User Timing:
 http://www.w3.org/2012/02/user-timing-lc-issues.html


It's not clear to me if we closed the loop on some of the issues raised for those specifications. It would be nice if the respective editors can go through those and give a status report on them.

Since we made plenty of changes to those specs, it would probably be good to republish them as a new LC draft before we move them to CR.

Thank you,

Philippe

PS: I created one for Performance Timeline but we haven't received any issues during the LC period.

Received on Wednesday, 7 March 2012 20:09:47 UTC