IRC log of webperf on 2013-04-24
Timestamps are in UTC.
- 16:54:01 [RRSAgent]
- RRSAgent has joined #webperf
- 16:54:01 [RRSAgent]
- logging to http://www.w3.org/2013/04/24-webperf-irc
- 16:54:03 [trackbot]
- RRSAgent, make logs world
- 16:54:03 [Zakim]
- Zakim has joined #webperf
- 16:54:05 [trackbot]
- Zakim, this will be WPWG
- 16:54:06 [trackbot]
- Meeting: Web Performance Working Group Teleconference
- 16:54:06 [trackbot]
- Date: 24 April 2013
- 16:54:07 [Zakim]
- I do not see a conference matching that name scheduled within the next hour, trackbot
- 16:55:38 [Alois]
- Alois has joined #webperf
- 16:57:46 [Aaron_MS]
- Aaron_MS has joined #webperf
- 16:59:06 [plh]
- zakim, this is per
- 16:59:06 [Zakim]
- ok, plh; that matches RWC_web-per()1:00PM
- 17:00:18 [Zakim]
- + +1.949.754.aabb
- 17:00:22 [Zakim]
- +[Microsoft.a]
- 17:00:39 [plh]
- I'm in the in HTML f2f meeting. please, let me know if I need to join the call and I will
- 17:01:03 [JatinderMann]
- present+ Alois, JatinderMann, RobDickenson, Aaron
- 17:02:33 [Zakim]
- + +1.408.203.aacc
- 17:05:08 [Zakim]
- + +1.650.214.aadd
- 17:05:23 [JatinderMann]
- present+ TonyG
- 17:05:56 [JatinderMann]
- Topic: Diagnostics and Error Logging
- 17:07:23 [JatinderMann]
- https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/NavigationErrorLogging/Overview.html
- 17:07:30 [JatinderMann]
- https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/ResourceErrorLogging/Overview.html
- 17:07:42 [tonyg]
- tonyg has joined #webperf
- 17:11:49 [JatinderMann]
- 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].
- 17:12:58 [DanielAustin]
- DanielAustin has joined #webperf
- 17:13:33 [DanielAustin]
- Greetings - sorry stuck in the HTML WG meeting
- 17:15:26 [JatinderMann]
- http://www.w3.org/TR/resource-timing/
- 17:15:31 [JatinderMann]
- 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]
- 17:15:43 [JatinderMann]
- Otherwise, this attribute must return the same value as fetchStart.
- 17:16:25 [JatinderMann]
- http://www.w3.org/TR/hr-time/#domhighrestimestamp
- 17:17:07 [Zakim]
- - +1.408.203.aacc
- 17:17:08 [Zakim]
- - +1.650.214.aadd
- 17:17:08 [Zakim]
- -[Microsoft.a]
- 17:17:09 [Zakim]
- - +43.664.853.aaaa
- 17:17:17 [JatinderMann]
- 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]
- 17:17:35 [JatinderMann]
- Jatinder: Please review the specs and give feedback. We can discuss in next week's call.
- 17:17:47 [JatinderMann]
- Jatinder: Tony, did the Chrome team finish their privacy and security reviews?
- 17:17:57 [JatinderMann]
- Tony: I believe they have not yet.
- 17:18:07 [Zakim]
- -[Microsoft]
- 17:18:23 [JatinderMann]
- Jatinder: Our review is still ongoing. We can discuss in a future call the details of the reviews once they are done.
- 17:18:30 [JatinderMann]
- Topic: Resource Priorities
- 17:18:42 [Zakim]
- - +1.949.754.aabb
- 17:18:43 [Zakim]
- RWC_web-per()1:00PM has ended
- 17:18:43 [Zakim]
- Attendees were +43.664.853.aaaa, [Microsoft], +1.949.754.aabb, +1.408.203.aacc, +1.650.214.aadd
- 17:37:59 [JatinderMann]
- Jatinder: Based on feedback on this thread, I have updated the spec draft with the following changes:
- 17:38:04 [JatinderMann]
- Jatinder: “defer” attribute has now been renamed to “delay” to differentiate from the existing “defer” attribute specified for the <script> element.
- 17:38:22 [JatinderMann]
- Jatinder: We may want to rename it to something else that doesn't sound like we're "delaying" the page.
- 17:38:33 [JatinderMann]
- Jatinder: Elements or objects with the “delay” attribute no longer delay the load event of the document from firing.
- 17:38:43 [JatinderMann]
- Jatinder: -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.
- 17:38:52 [JatinderMann]
- Topic: Resource Timing
- 17:39:12 [JatinderMann]
- Jatinder: Microsoft has reviewed the Resource Timing test cases. We'll send out detailed notes this coming week.
- 17:39:15 [JatinderMann]
- rrsagent, generate minutes
- 17:39:15 [RRSAgent]
- I have made the request to generate http://www.w3.org/2013/04/24-webperf-minutes.html JatinderMann
- 19:13:16 [Zakim]
- Zakim has left #webperf