17:15:00 <RRSAgent> RRSAgent has joined #webperf
17:15:00 <RRSAgent> logging to http://www.w3.org/2012/11/09-webperf-irc
17:15:02 <trackbot> RRSAgent, make logs world
17:15:02 <Zakim> Zakim has joined #webperf
17:15:04 <trackbot> Zakim, this will be WPWG
17:15:04 <Zakim> I do not see a conference matching that name scheduled within the next hour, trackbot
17:15:05 <trackbot> Meeting: Web Performance Working Group Teleconference
17:15:05 <trackbot> Date: 09 November 2012
17:15:09 <simonjam_> simonjam_ has joined #webperf
17:15:34 <JatinderMann> present: James, Arvind, Jason, Philippe, Jatinder, Alois
17:16:29 <plh> plh has joined #webperf
17:16:32 <plh> http://w3c-test.org/webperf/tests/submission/W3C/NavigationTiming/nt-idlharness.html
17:17:19 <JatinderMann> Topic: Navigation Timing Status
17:21:16 <JatinderMann> plh: Running with these tests, IE10 passes 75/81 tests and Firefox passes most as well. I recommend we speak with the Director to move Navigation Timing to Recommendation.
17:21:22 <plh> https://w3c-test.org/webperf/tests/submission/W3C/HighResolutionTime/hrt-idlharness.html
17:22:09 <plh> https://w3c-test.org/webperf/tests/submission/W3C/ResourceTiming/rt-idlharness.html
17:23:41 <JatinderMann> Topic: Resource Timing
17:24:50 <JatinderMann> https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/ResourceTiming/Overview.html
17:26:42 <JatinderMann> James: We should update "This section is non-normative." text in Navigation and Resource Timing to "This illustration is non-normative."
17:28:32 <plh> done
17:29:53 <plh> plh has changed the topic to: webperf f2f - Paul, Ganesh, please ping us if you want to call in
17:40:08 <JatinderMann> ACTION Jatinder Follow up on the expected behavior when two documents request the same resource; how do the timelines look
17:40:09 <trackbot> Created ACTION-107 - Follow up on the expected behavior when two documents request the same resource; how do the timelines look [on Jatinder Mann - due 2012-11-16].
17:52:51 <JatinderMann> Topic: RequestAnimationFrame
17:52:52 <JatinderMann> https://developer.mozilla.org/en-US/docs/DOM/window.mozAnimationStartTime
17:55:09 <JatinderMann> Jatinder: Both IE and Firefox implement window.animationStartTime (Firefox with prefix). I'll follow up the Editor's to close on this.
17:55:23 <plh> http://w3c-test.org/webperf/tests/submission/Intel/user-timing/
18:01:38 <plh> https://www.w3.org/2002/09/wbs/1/webperf2012/?login
18:12:48 <plh> for HAR, Arvind will keep thinking about it
18:13:14 <plh> James: for memory mangement, we have some privacy concern
18:13:47 <plh> ... ie can figure if someone is logged in into a service based on heapsize
18:15:00 <plh> ... ie you put the service into an iframe, then look at the heapsize
18:15:21 <plh> Alois: you can ask for user permission
18:15:43 <plh> James: they wouldn't know what the question meant...
18:15:55 <plh> Jason: I'd like to do something related to memory
18:16:30 <plh> ... ie offering reclaim pattern
18:17:05 <plh> ... ie a memory usage pattern where the runtime monitors resources and efficiencly garbage it
18:17:18 <pbakaus> all: I am here and following, but might not be able to call in. If you have specific questions for me, ping me
18:17:21 <plh> Alois: but you'll want to know if you're leaking memory or not
18:17:27 <plh> Paul, ok
18:17:53 <plh> Jason: a dev shoulnd't have to worry about memory
18:18:12 <plh> Alois: but we make bugs, I'd like to know if I'm retaining a reference
18:18:21 <plh> James: would help to break this into use cases
18:19:04 <plh> Jatinder: let's going through the survey results
18:19:37 <simonjam> simonjam has joined #webperf
18:20:23 <plh> Jatinder: adaptive sreaming api...
18:20:34 <plh> ... people just want to know what
18:20:39 <plh> ... connection is used
18:20:51 <plh> http://dvcs.w3.org/hg/html-media/raw-file/tip/media-source/media-source.html
18:22:10 <plh> Jatinder: Resource Timing 2 needs to cover video as a post processing timing measurements
18:23:21 <plh> Jatinder: above the fold
18:23:27 <plh> Jatinder: Frame rate
18:23:33 <plh> Jatinder: AnimationStartTime
18:23:38 <plh> Jatinder: <video?
18:23:49 <plh> Jatinder: setImmediate
18:24:07 <plh> Jatinder: Memory: GC, info, leak, profiling
18:30:05 <plh> http://www.ietf.org/rfc/rfc3229.txt
18:33:04 <plh> we're classifying things into three buckets for the next charter
18:33:17 <plh> In: Beacon (ie send me those stuff when you have time)
18:33:49 <plh> Toss the ball: Client Hints
18:34:17 <plh> Out means "drop it"
18:34:28 <plh> Toss the ball means "find someone else to do it"
18:34:41 <plh> Toss the Ball, Client Hints, Delta Delivery
18:34:51 <plh> s/Ball,/Ball:/
18:35:06 <plh> Out: Timings in Header
18:36:23 <plh> Maybe: Diagnostics
18:37:23 <plh> s/three/four/
18:47:55 <plh> s/Maybe: Diagnostics/In: Diagnostics (Leaks, etc.)/
18:50:29 <plh> s/Leaks/Leaks, Errors/
18:50:42 <pbakaus> plh, where are Client Hints going to be tossed to? IETF?
18:51:11 <plh> we didn't talk about it further.
18:51:24 <pbakaus> ok thanks
18:51:30 <plh> IETF yes
18:51:32 <plh> DAP maybe
18:51:58 <plh> Delta Delivery seems clearly in IETF to me
18:52:08 <pbakaus> yes, agreed
18:52:21 <plh> Out: GC
18:53:03 <pbakaus> （╯°□°）╯ ︵ ┻━┻
18:53:51 <plh> not sure how we should interpret this answer :)
18:54:17 <pbakaus> hehe. Sad about GC, but all things asset memory are more important to us.
18:54:49 <plh> Toss the ball: device capability: CPU, Memory size, etc.
18:55:30 <plh> Out: Memory Heap
18:55:51 <RRSAgent> I have made the request to generate http://www.w3.org/2012/11/09-webperf-minutes.html plh
18:55:59 <Alois> but part of heap dump
18:56:50 <Alois> sorry meant diag
18:57:19 <plh> s/dump/diag/
19:04:54 <plh> In: Resource Priority
19:06:04 <plh> Out: background throlling
19:07:05 <plh> Out: Idleness
19:07:28 <plh> Maybe: HAR
19:10:23 <plh> In; .defer attribute
19:11:55 <plh> (within Resource Priorities: existing attributes, such .defer or prefetch)
19:12:52 <plh> In: Pre-fetching
19:15:26 <plh> https://support.google.com/analytics/bin/answer.py?hl=en&answer=1008080
19:16:43 <plh> http://www.w3.org/TR/html5/links.html#link-type-prefetch
19:17:22 <plh> s/In: Pre-fetching//
19:20:00 <plh> In: Pre-render
19:21:21 <plh> Out: Above the fold
19:24:50 <Zakim> Zakim has left #webperf
19:27:23 <plh> In: Display Perf
19:30:01 <pbakaus> plh, what is Display Perf referring to?
19:30:34 <plh> framerate, throughput
19:31:02 <plh> Toss the ball: Realtime Video/Streaming Perf
19:31:16 <plh> In: Resource Timing 2 (ie postprocessing)
19:32:02 <plh> http://lists.w3.org/Archives/Public/public-webrtc/2012Jun/0239.html
19:36:53 <plh> *.toJSON to be considered in our specs
19:40:13 <plh> (we're now talking about setImmediate)
19:42:33 <plh> In: setImmediate
19:44:33 <plh> In: Timing in Web Workers
19:48:02 <Alan> Alan has joined #webperf
19:48:06 <plh> Maybe: Async scroll
19:49:03 <plh> Toss the ball: Best Practices (Steve)
19:53:01 <plh> s|setImmediate|setImmediate/Power|
20:03:01 <plh> Beacon: Alois, Jatinder
20:03:09 <plh> Diagnostics: Alois, Jatinder
20:03:24 <plh> Resource Priorities: Jatinder
20:03:34 <plh> Pre-render: Arvind
20:03:41 <plh> Display perf: Jason
20:03:58 <plh> Resource Timing 2: Arvind
20:04:13 <plh> setImmediate/Power: Jason
20:04:20 <plh> Timing in WebWorker: Jatinder
20:47:09 <plh> plh has joined #webperf
20:47:44 <RRSAgent> I have made the request to generate http://www.w3.org/2012/11/09-webperf-minutes.html plh
22:04:26 <plh_> plh_ has joined #webperf
22:11:19 <plh> plh has joined #webperf
22:11:39 <plh> plh has changed the topic to: We're done for the week!