See also: IRC log
<trackbot> Date: 06 July 2011
<scribe> scribe: Jatinder Mann
present_ Jatinder Mann
Jatinder: Any particular feedback on the setImmediate spec we want to discuss first?
James: Per my mailing list question, I had some concerns regarding the clamping.
Jason: I had just sent a response
to you on the mailing list prior to the call starting.
... you had some questions on my historical account, what in
particular are you referring to?
James: Questions about the historical account on when clamping was introduced.
https://bugzilla.mozilla.org/show_bug.cgi?id=123273
Jason: We are excited about setImmediate, we want to have an API to that helps with power efficiency, including on intel and arm chips.
James: Do you think this will let us remove the clamp?
Jason: Yes, absolutely.
... We would love to get to a pattern where the clamp is
removed for sites that use these apis, allowing for better
efficiency.
... this may also help Chrome in Speedstep, as the 4ms clamp is
probably impacting your implementation. You should be able to
see this in the Power Consumption blog post we wrote a few
months ago.I can respond on the mail.
James: If you can send specific examples that'll be great.
Jason: Any other questions on setImmediate or can we move on to requestAnimationFrame?
<plh> http://www.w3.org/2010/webperf/track/issues/raised
Jatinder: Per discussion in last week’s call, the requestAnimationFrame has 7 open issues in it that are blocking the spec from going to last call. Most of these issues, as discussed, do have relative consensus in the group and just need to be specified in the spec. Cameron, James, if you are overbooked and need any help with updating the spec, I am more than willing to help you. Please let me know.
James: Issues 6 and 7 can be closed, as there are no spec changes required.
<plh> issue-6?
<trackbot> ISSUE-6 -- (duplicate callbacks): Spec needs to clarify expected behavior for duplicate calls of the same callback [Request Animation Frame] -- raised
<trackbot> http://www.w3.org/2010/webperf/track/issues/6
<plh> issue-7?
<trackbot> ISSUE-7 -- FrameRequestCallback interface should be designated as Callback=FunctionOnly -- raised
<trackbot> http://www.w3.org/2010/webperf/track/issues/7
James: Issues 2 and 4 may need more time to write the text here.
Jason: Issue one (scheduling callbacks) could become a compat issue if it isn't well defined in the spec.
Jatinder: We discussed in the past that we can either do no callbacks, an expontial backoff or a throttled callback. We discussed whether to make this optional or normative. I recommend we make this a normative requirement to ensure implementations are interoperable.
James: Agreed.
... I prefer no callbacks, as that is most efficient.
Jason: Agree that we shouldn't do callbacks.
James: Cameron, can you see if there are any concerns on your end with not issuing any callbacks?
Jatinder: If I recall, some concerns with no callbacks was that the animation wouldn't be drawn. However, if you do time based animation and you use the timestamp parameter, the callback shouldn't matter, as the animation would be drawn at the proper place when visible.
James: Agreed.
Cameron: I will respond to the mailing list with this option and see if Boris or others have any concerns.
James: I plan on closing most of the editorial issues soon.
Jatinder: Once we have resolution on the issues, we can move towards taking this spec to last call.
Cameron: What does the charter suggest?
Jatinder: Charter suggests August 2011 to enter Last Call.
Cameron: This seem reasonable.
Jatinder: Per action items from last week, the Page Visibility spec has been updated to include a section on Vendor Prefixes and to remove the PAGE_PRERENDER state. Per WG decision, we plan on taking this spec to last call on 7/13.
Arvind: Has there been any feedback on the spec?
Jatinder: None on the mailing list.
Arvind: Great.
Jatinder: TPAC 2011 will be a great opportunity for the Web Performance WG to touch base on the current status of the specs, and to network with other groups in the area. Philippe, per your request last week, can we arrange something?
Philippe: What does works best? One day or two?
Arvind: 1 day. Indifferent which day.
Jason: Agreed, one day.
Philippe: Let's look at the Thursday.
Jatinder: Thanks. If no other issues, let's see everyone next week. Thanks!
This is scribe.perl Revision: 1.136 of Date: 2011/05/12 12:01:43 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 Found Scribe: Jatinder Mann Default Present: [Microsoft], Philippe, heycam, jamesr, +1.503.264.aaaa, +1.650.253.aabb Present: [Microsoft] Philippe heycam jamesr +1.503.264.aaaa +1.650.253.aabb Jatinder Mann Cameron McCormack Le Hegaret James Robinson WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Found Date: 06 Jul 2011 Guessing minutes URL: http://www.w3.org/2011/07/06-webperf-minutes.html People with action items:[End of scribe.perl diagnostic output]