<trackbot> Date: 11 January 2012

Topics: Spec and Test Updates from last week

Jatinder: Karen and I have updated the Page Visibility, and Timing specs to complete Action items 59, 61, 64 and 74.
... Please review those changes.
... Karen has pushed out two test cases in Action 21 and 75.

Close ACTION 19

http://www.w3.org/2010/webperf/track/actions/18

<plh> close action-19

<trackbot> ACTION-19 Investigate tests around persistent connections closed

http://www.w3.org/2010/webperf/track/actions/19

Arvind: Let's go through Navigation Timing open items and see what remains.

<plh> close action-19

<trackbot> ACTION-19 Investigate tests around persistent connections closed

Tony: I'm inclined to say that persistent connections isn't a part of HTML5 spec and probably can't be tested. Let's close

close action-18

<trackbot> ACTION-18 Follow up on test coverage and propose new test cases. closed

http://www.w3.org/2010/webperf/track/actions/57

http://www.w3.org/2010/webperf/track/actions/75

http://w3c-test.org/webperf/tests/approved/navigation-timing/html5/test_timing_attributes_order.html

Tony: Future test cases should always go to submission folder for review prior to moving to approval folder.

Jatinder: Let's keep action-75 open so that we can fix the typo thats causing the test to fail.

<plh> http://w3c-test.org/webperf/tests/approved/navigation-timing/html5/test_navigation_type_reload.html

Jatinder: Karen to update test_navigation_type_reload.html and test_timing_attributes_order.html to fix the resource issue and Tony will review.

http://lists.w3.org/Archives/Public/public-web-perf/2012Jan/0008.html

Jatinder: What are the WG's thoughts on client authentication modal dialogs? Users could impact aggregate timing by sitting on a modal dialogs.

Tony: There are other slow javascript dialogs, alerts that could also impact the overall timing.

Jatinder: I don't think we would want to throw away the client authentication time, as the overall performance timeline shouldn't be impacted. Our options might be to include a new phase.
... we expect the client authentication dialogs to occur between connectStart and responseEnd.

Arvind: HTTP Client authentication might have smaller usage as time goes on.
... We should be able to get data to see how many webpages in the world use this feature.

Tony: We need a spec update here regardless. Either we add the new phases or how our current phases work around this.

Arvind: Well, the problem still exists for proxy servers. There may be many more such small edge cases like this.
... Either we create a new parallel time for authentication. I don't think we should broaden the scope of redirects.

Jatinder: Arvind will follow up with data on how common these issues are and see if we even want to make any change here.

Arvind: I think we should target getting this spec to PR.

Jatinder: Let's plan to update all test cases for next week and target entering PR then.

Tony: I agree with that plan.

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.

Default Present: +1.404.978.aaaa, [Microsoft], +1.650.253.aabb, Plh, chris
Present: +1.404.978.aaaa [Microsoft] +1.650.253.aabb Plh chris TonyG Arvind JatinderMann KarenAnderson plh

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

Found Date: 11 Jan 2012
Guessing minutes URL: http://www.w3.org/2012/01/11-webperf-minutes.html
People with action items: 

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