W3C

- DRAFT -

Web Performance Working Group Teleconference

29 Jun 2011

See also: IRC log

Attendees

Present
+1.650.253.aaaa, [Microsoft], Plh, Ian, JatinderMann, NicJansma, Annie, Sullivan, Karen, Anderson, JamesS, TonyG, Philippe
Regrets
Chair
SV_MEETING_CHAIR
Scribe
JatinderMann

Contents


<trackbot> Date: 29 June 2011

<plh> typo in http://ie.microsoft.com/testdrive/HTML5/Forms/Default.html

<plh> "(avaiable in increments of 10) "

I'm excited to announce the second IE10 Platform Preview was released today with support for requestAnimationFrame, Page Visibility and setImmediate. I'd like to thank the working group for designing these specs.

Jatinder: I will have an updated draft for the specs incorporating the inheritance model before the end of this week for your review.

Zhiheng: I had some feedback on the getMarks and getMeasures APIs on the User Timing spec. Some clarification questions that may be resolved with your updates.
... Just wanted to let everyone know that FF7 will support Navigation Timing.

Tony: Sorry, I wasn't able to make last week's call. Is the current proposal the one discussed in Nic's last mail?

Nic: Yes, that's the one. We're working on making updates to the spec and then send out broadly.

Technical meeting at Santa Clara end of October, beginning of November. The Web Application WG Mon Tues Wed, HTML5 WG on Thurs and Fri. Unfortunately, we missed the deadline for getting a room. But if we’re interested I could schedule something for Thursday.

Due to the vacations next week, we will be cancelling the first half of next week's web performance teleconference.

Jatinder: We uploaded the setImmediate spec to the mailing list yesterday. Has everyone had a chance to take a look at the spec?

Arvind: We are still taking a look at the spec internally at Google. We can send follow up mail with feedback, as we come with them.

Jason: Considering there are three implementations of requestAnimationFrame, two implementations of Page Visibility, and one for setImmediate we should start looking into locking down the spec. Why don't we go through the action items?

Jatinder: Based on last week's call, we went through all 7 of the requestAnimationFrame open issues. Most of these are well understood and are just waiting on the editors to make changes.

Arvind: I will follow up with James to see if he's planning on making changes soon.

Jatinder: For Page Visibility, there was one major open item: whether or not to include the visibilityState attribute. Based on the mailing list, it appears that there is value in keeping visiblityState as a host for future visibility states or vendor prefixed states. We may want to leave the spec as is.
... There is one action item remaining to include a section on the expected vendor prefixed syntax, I will add that section.

Arvind: Considering prerender is only in a single vendor and is optional anyway, we should just remove the prerender state.

Jatinder: Agree.
... I will keep the PAGE_PREVIEW state as an optional visibility state.

Arvind: What is the plan for testing our implementations to make sure they are interoperable?

Jatinder: The test suite will help there. I will take an action to release a page visibility test case.
... Considering the spec is very stable, we will have a test suite, we should consider taking the spec to last call.

Arvind: I agree we should take it to last call.

Jatinder: How about we enter Page Visibility Last Call on July 13th? That will give time to finish making the changes to the spec and test suite next week and another week prior to moving to last call.

Arvind: Agreed.

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.136 (CVS log)
$Date: 2011/06/29 22:31:41 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
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
Inferring Scribes: JatinderMann

WARNING: No "Topic:" lines found.


WARNING: Replacing list of attendees.
Old list: James [Microsoft] Plh
New list: +1.650.253.aaaa [Microsoft] Plh Ian

Default Present: +1.650.253.aaaa, [Microsoft], Plh, Ian
Present: +1.650.253.aaaa [Microsoft] Plh Ian JatinderMann NicJansma Annie Sullivan Karen Anderson JamesS TonyG Philippe

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

Found Date: 29 Jun 2011
Guessing minutes URL: http://www.w3.org/2011/06/29-webperf-minutes.html
People with action items: 

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


WARNING: No "Topic: ..." lines found!  
Resulting HTML may have an empty (invalid) <ol>...</ol>.

Explanation: "Topic: ..." lines are used to indicate the start of 
new discussion topics or agenda items, such as:
<dbooth> Topic: Review of Amy's report


[End of scribe.perl diagnostic output]