W3C home > Mailing lists > Public > public-web-perf@w3.org > January 2012

[minutes] 2012-01-18 Web Performance WG Teleconference #58

From: Jatinder Mann <jmann@microsoft.com>
Date: Wed, 18 Jan 2012 18:51:28 +0000
To: "public-web-perf@w3.org" <public-web-perf@w3.org>
Message-ID: <EE4C13A1D11CFA49A58343DE361B0B04136E9B29@TK5EX14MBXC253.redmond.corp.microsoft.com>
Meeting Summary:



1.      Navigation Timing to PR

In order to take the Navigation Timing specification to PR, we need to ensure all of our test case open action items are closed. The WG had agreed last week to take Navigation Timing to PR today, however, we still have two remaining action items that need to be closed, listed below. As soon as these action items are closed, either via email or by next week's conference call, we can move this spec to PR.



a.       ACTION 77 - Update the test_navigation_type_reload.html to fix the compare issue

The reload redirectEnd and reload redirectStart portions of this test are failing on both IE and Chrome. We expect this to be a test case bug where we are incorrectly doing the comparison. Further, there is a msFirstPaint test that should be removed, as that attribute is not a part of the Navigation Timing spec. James has taken the action to update this bug.



b.       ACTION 21 and 75 need review

Tony has taken an action item to review the changes Karen has made to test_navigation_type_reload.html test case to address ACTION-21 and test_timing_attributes_order.html and blank_page_unload.html test cases to address ACTION-75. Tony has mentioned he will do this review in mail this week.



                        The following action item was closed:



c.        ACTION 76 - Test case to test NavigationStart attribute has been closed.

We closed ACTION 76, as another test is already testing this attribute, as per notes in the action item - http://www.w3.org/2010/webperf/track/actions/76.


Detailed Notes:



Web Perf Teleconference #58 1/18/2012



IRC log: http://www.w3.org/2012/01/18-webperf-irc


Meeting Minutes: http://www.w3.org/2012/01/18-webperf-minutes.html



Attendees

Present for Navigation Timing, Resource Timing and User Timing (4-5PM EST/1-2PM PST)

Philippe Le Hegaret, Jatinder Mann, Arvind Jain, Karen Anderson, Zhiheng Wang, James Simonsen, Alois


Present for Page Visibility, Efficient Script Yielding, Display Paint Notifications (4-5PM EST/2-3PM PST)

Meeting cancelled.



Scribe

Jatinder Mann



Contents

Agenda

1.       Discuss Navigation Timing to PR



--------------------------------------------------------------------------------



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> 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.

Jatinder: Action-77 was created on James to update the test_navigation_type_reload.html compare issue
Received on Wednesday, 18 January 2012 18:52:37 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:04:32 UTC