See also: IRC log
<trackbot> Date: 18 January 2012
<plh> zaki,, list conferences
Jatinder: Karen updated notes on Action 76 - http://www.w3.org/2010/webperf/track/actions/76
Karen: Was there an issue before?
James: I'm not clear on the details from before. But I think we can close it out now.
close action-76
<trackbot> ACTION-76 Add a Navigation Timing test case to test NavigationStart. closed
<Karen> I'll go ahead and resolve the AI
<plh> http://w3c-test.org/webperf/tests/approved/navigation-timing/html5/test_timing_attributes_order.html
plh: This test used to work in Chrome but it no longer works. Do we know why?
Karen: The only change to this test was adding the beforeunload, I don't believe we changed the load.
James: We still need to look into this and see why this is the case.
Karen: Regarding the document readiness test case, I looked and seems like IE doesn't support all those events for iframes.
<plh> "If the current document readiness changes to the same state multiple times, domLoading, domInteractive, domContentLoadedEventStart, domContentLoadedEventEnd and domComplete must return the time of the first occurrence of the corresponding document readiness change."
plh: I think we are fine with this test, as we are not relying on any of these events specifically. A HTML5 change here should not impact Navigation Timing.
http://w3c-test.org/webperf/tests/approved/navigation-timing/html5/test_navigation_type_reload.html
James: Seems like the redirectEnd greater than test may be wrong.
Karen: Do we think all of these are greater than and equal?
James: I believe the whole point was to make sure that the values change after the reload.
Zhiheng: Even msFirstPaint test is failing.
Jatinder: We should remove that
test as its not a part of the spec.
... On IE9 I can see that msFirstPaint, redirectEnd and
redirectStart are failing.
plh: Previously, I saw these tests pass on IE9.
James: Is it possible that the test harness changed from underneath?
plh: This is possible.
<Karen> msFirstPaint is not a must property...we should remove it
<plh> wp_test(function () { assert_true(value > greater_than, msg); }, msg);
Karen: I don't think its a problem with the assert, I think its the test itself.
<Karen> The test is doing a deep compare of all of the timings and checking the new value is greater than the old value...there is not a redirect so 0 will not be > 0
plh: We need to ensure that IE and Chrome need to run all the tests and ensure that we pass on all of them.
<plh> nope, not me :)
<plh> who is clown?
Action SimonJam Update the test_navigation_type_reload.html to fix the compare issue
<trackbot> Sorry, couldn't find user - SimonJam
Action Update the test_navigation_type_reload.html to fix the compare issue
<trackbot> Sorry, couldn't find user - Update
Action simonjam Update test_navigation_type_reload.html to fix the compare issue
<trackbot> Sorry, couldn't find user - simonjam
<plh> test_timing_attributes_order and test_navigation_type_reload for chrome
<plh> test_navigation_type_reload for IE
http://w3c-test.org/webperf/tests/approved/navigation-timing/html5/test_timing_xserver_redirect.html
plh: This is passing in IE10.
Action-77 was created on James
scribe: to update the test_navigation_type_reload.html compare issue
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.425.654.aaaa, +1.650.253.aabb, +1.425.681.aacc, Plh, clown, +43.732.908.2aadd, +1.503.203.aaee Present: +1.425.654.aaaa +1.650.253.aabb +1.425.681.aacc Plh clown +43.732.908.2aadd +1.503.203.aaee simonjam alois karenand plh JatinderMann ArvindJain Zhiheng WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Found Date: 18 Jan 2012 Guessing minutes URL: http://www.w3.org/2012/01/18-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[End of scribe.perl diagnostic output]