19:50:51 RRSAgent has joined #webperf 19:50:51 logging to http://www.w3.org/2011/06/22-webperf-irc 19:50:53 RRSAgent, make logs world 19:50:53 Zakim has joined #webperf 19:50:55 Zakim, this will be WPWG 19:50:55 ok, trackbot; I see RWC_web-per(WPWG)4:00PM scheduled to start in 10 minutes 19:50:56 Meeting: Web Performance Working Group Teleconference 19:50:56 Date: 22 June 2011 19:51:14 scribe: Jatinder Mann 19:51:18 present+ Jatinder Mann 20:01:36 RWC_web-per(WPWG)4:00PM has now started 20:01:44 + +1.650.691.aaaa 20:01:53 zhiheng has joined #webperf 20:01:55 +James 20:02:20 simonjam has joined #webperf 20:02:28 present+ Zhiheng Wan 20:02:34 present+ JamesS 20:02:41 present+ Nic Jansma 20:02:49 +[Microsoft] 20:05:07 present+ Karen Anderson 20:05:57 Jatinder: As per last week’s action items, we had sent out a proposal that combined inheritance with the current spec: http://lists.w3.org/Archives/Public/public-web-perf/2011Jun/0075.html. 20:06:14 Jatinder: What are your thoughts? 20:06:22 James: I liked it a lot. 20:06:29 Zhiheng: It looks cool! 20:08:42 plh has joined #webperf 20:08:48 +Plh 20:09:09 Zhiheng: Thoughts about Jatinder's suggestion about putting them into different namespace? 20:09:43 Jatinder: That was an initial suggestion to give structure. I feel that the current proposal gives us that structure. 20:09:59 James: I agree that the new proposal takes care of that. 20:10:03 Zhiheng: Ok. 20:11:17 Jatinder: We may want to go ahead and make changes to Navigation Timing to include the unified behavior and then solicit feedback from the mailing list. 20:11:38 -[Microsoft] 20:11:50 zhiheng has joined #webperf 20:12:01 +[Microsoft] 20:13:11 James: Are there any other mailing list that have more traffic to give feedback? 20:13:34 phl: We can use Web Apps, but they may not give feedback here. 20:15:06 Jatinder: Is there any impact on Navigation Timing spec if we add the new interfaces? 20:15:55 phl: It will remain in PR, it would not necessarily go to CR, but it would be one month in LC. 20:20:58 Jatinder: If we go to LC, aren't we opening all areas of the spec to question, not just the delta? 20:22:04 -James 20:22:06 -[Microsoft] 20:22:07 -Plh 20:22:07 - +1.650.691.aaaa 20:22:09 RWC_web-per(WPWG)4:00PM has ended 20:22:11 Attendees were +1.650.691.aaaa, James, [Microsoft], Plh 20:24:18 phl: We can set the bar higher for existing portions of the spec and focus feedback on the deltas. 20:29:26 phl: We may also want to add prototype tests to the test suites now that the prototype is not as simple as before. 20:29:31 Karen: Agreed. 20:30:30 The WG agrees to update the Navigation Timing spec to add the current unified proposal sent last week and send that out for additional feedback. Jatinder will send some text to Zhiheng to consider adding to the spec. 21:01:21 RWC_web-per(WPWG)4:00PM has now started 21:01:28 +[Microsoft] 21:01:36 +??P4 21:01:39 Zakim, ??P4 is me 21:01:39 +heycam; got it 21:04:10 Topic: Discuss Battery Status specification feedback. 21:04:16 Jatinder: Let’s discuss feedback on the Battery Status spec: http://dev.w3.org/2009/dap/system-info/battery-status.html 21:04:58 Jatinder: Seems like a very simple API set: “isPlugged” gives you whether the device is on battery, “level” gives you a scaled representation from 0 – 100 of your battery level, and batterystatus gets fired when the battery status changes (level varies by 1% or isPlugged changes). 21:06:07 Jatinder: Not sure of the value of initBatteryStatusEvent(). Similar idea to the initEVent() in DOM Level 2 and 3 specs, http://www.w3.org/TR/DOM-Level-2-Events/events.html#Events-Event-initEvent. 21:08:59 +Plh 21:09:01 The WG is relatively happy with the spec based on description on the call. 21:09:10 Topic: Discuss requestAnimationFrame open issues. 21:09:22 Jatinder: Let’s go through each open issue on requestAnimationFrame and get an update from the editors - http://www.w3.org/2010/webperf/track/issues 21:09:57 http://www.w3.org/2010/webperf/track/products/5 21:11:15 ISSUE-1: Scheduling processing model needs to be more tightly defined 2011-05-18 21:11:15 ISSUE-1 Scheduling processing model needs to be more tightly defined notes added 21:11:34 Cameron: Needs to be tightened up. Otherwise no real issues. 21:11:39 Jatinder: We don’t have any issues here. 21:11:59 Next: Callback time parameter needs definition 2011-05-18 21:13:56 + +1.650.253.aaaa - is perhaps Arvind? 21:14:31 Nic: Are we defining the exact time that the frame was going to be drawn? 21:14:39 Cameron: Yes. 21:14:44 Nic: In the case that the callback takes more than one refresh rate, we may want to rely on the previous frame instead the next frame. 21:14:49 Cameron: Since they are clock times, it shouldn’t matter. Maybe we should use the clock tick time. 21:15:21 Next: Animation frame times should be monotonically increasing 2011-05-18 21:16:09 http://www.w3.org/TR/navigation-timing/#mono-clock 21:18:43 Nic: If I remember correctly on the list, as long as the timestamp parameter is also monotonically increasing, this would make sense. 21:20:02 Jatinder: This issue should also consider including window.animationStartTime. 21:20:08 Cameron: Yes. 21:20:45 Next: We perhaps should support an element parameter to requestAnimationFrame() 21:20:53 Jatinder: We should consider making this optional. 21:21:12 Nic: It would be hard to do feature detection for an optional argument 21:23:32 Jatinder: This argument defines element visibility. Web developers should a graceful fallback to visible. 21:23:41 Next: Expected callback rates should be documented 2011-05-18 21:24:32 Cameron: We had agreed that the expected callback rate should match the display refresh rate. We would probably not want to make this a must statement, but rather should. 21:24:36 Jatinder: Agree. 21:24:48 Next: Spec needs to clarify expected behavior for duplicate calls of the same callback 2011-05-25 21:25:03 Jatinder: I believe everyone on the list agreed to duplicate callbacks. 21:25:08 Cameron: Yes. 21:25:17 Next: FrameRequestCallback interface should be designated as Callback=FunctionOnly 21:26:43 Cameron: Whatever WebIDL defines, requestAnimationFrame should follow, since this issue isn't local to just requestAnimationFrame. 21:26:50 Jatinder: Agreed. 21:28:54 Jatinder: Considering there are two implementations for this spec, and we are all relatively in agreement with the design, I expect this spec to move quickly. When do we expect to have all these issues completed by? 21:28:58 Cameron: I been busy of late. Will discuss with James further. Hopefully, I will start making changes next week. 21:29:21 http://www.w3.org/mid/4DF60DEF.7060005@labri.fr 21:30:28 https://mail.mozilla.org/pipermail/es-discuss/2011-March/013227.html 21:32:48 Cameron: David brought up this issue, which should be raised as an issue. 21:33:26 -[Microsoft] 21:33:28 -Plh 21:33:29 -heycam 21:34:08 -Arvind? 21:34:09 RWC_web-per(WPWG)4:00PM has ended 21:34:11 Attendees were [Microsoft], heycam, Plh, +1.650.253.aaaa 21:36:03 rrsagent, create minutes 21:36:03 I have made the request to generate http://www.w3.org/2011/06/22-webperf-minutes.html JatinderMann 21:54:50 zakim, please part 21:54:50 Zakim has left #webperf 21:54:55 rrsagent, please part 21:54:55 I see no action items