Re: Action 99: Update test_timing_attributes_order test and document_readiness_exists investigations

Hi Karen, Thanks for the updates.

*
> http://w3c-test.org/webperf/tests/submission/Microsoft/NavigationTiming/test_timing_attributes_order.htm
> *<http://w3c-test.org/webperf/tests/submission/Microsoft/NavigationTiming/test_timing_attributes_order.htm>
>

Looks good to me.


> *
> http://w3c-test.org/webperf/tests/submission/Microsoft/NavigationTiming/test_document_readiness_exist.html
> *<http://w3c-test.org/webperf/tests/submission/Microsoft/NavigationTiming/test_document_readiness_exist.html>
>

This test checks that document.readyState has the right value at the right
time. That's fine, but isn't related to Navigation Timing. To make it
relevant, we should verify that each of
performance.timing.{domLoading,domInteractive,domComplete} are 0 prior to
reaching each readiness phase and are >0 after reaching it.

-Tony