<trackbot> Date: 24 April 2013

<plh> I'm in the in HTML f2f meeting. please, let me know if I need to join the call and I will

Diagnostics and Error Logging

https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/NavigationErrorLogging/Overview.html

https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/ResourceErrorLogging/Overview.html

Jatinder: Based on feedback from the working group, we felt that we needed a separate interface for historical error data related to the document errors, and for errors on the current document. Based on this feedback, I have uploaded drafts for the Navigation Error Logging [1] and Resource Error Logging [2] specifications. These two specifications are designed to replace the current Error Logging spec draft [3].

<DanielAustin> Greetings - sorry stuck in the HTML WG meeting

http://www.w3.org/TR/resource-timing/

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 or the Timing-Allow-Origin HTTP response header rules are met, this attribute must return the same value as redirectStart. Otherwise, this [CUT]

Otherwise, this attribute must return the same value as fetchStart.

http://www.w3.org/TR/hr-time/#domhighrestimestamp

Jatinder: Also, instead of defining a buffer clearing and setting method for each type of object that has a buffer, I recommend we should update Performance Timeline to define a clearData(DOMString entry) and setBufferSize(DOMString entry, unsigned long maxSize) method, where entry is a type of PerformanceEntry object buffer that is to be set. This method would currently apply to PerformanceResourceTiming, ResourceErrorLogging, and NavigationEr[CUT]
... Please review the specs and give feedback. We can discuss in next week's call.
... Tony, did the Chrome team finish their privacy and security reviews?

Tony: I believe they have not yet.

Jatinder: Our review is still ongoing. We can discuss in a future call the details of the reviews once they are done.

Resource Priorities

Jatinder: Based on feedback on this thread, I have updated the spec draft with the following changes:
... “defer” attribute has now been renamed to “delay” to differentiate from the existing “defer” attribute specified for the <script> element.
... We may want to rename it to something else that doesn't sound like we're "delaying" the page.
... Elements or objects with the “delay” attribute no longer delay the load event of the document from firing.
... - User Agents may further delay downloading resources of elements or objects with the “delay” attribute if their bounding box is outside of the viewport or their display property is set to none.

Resource Timing

Jatinder: Microsoft has reviewed the Resource Timing test cases. We'll send out detailed notes this coming week.

This is scribe.perl Revision: 1.137  of Date: 2012/09/20 20:19:01  
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, [Microsoft], +1.949.754.aabb, +1.408.203.aacc, +1.650.214.aadd
Present: +43.664.853.aaaa [Microsoft] +1.949.754.aabb +1.408.203.aacc +1.650.214.aadd Alois JatinderMann RobDickenson Aaron TonyG

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

Found Date: 24 Apr 2013
Guessing minutes URL: http://www.w3.org/2013/04/24-webperf-minutes.html
People with action items: 

WARNING: Input appears to use implicit continuation lines.
You may need the "-implicitContinuations" option.