RE: [agenda] Web Performance WG Teleconference #24 Agenda 2011-03-09

Hi Tony,



It looks like the timing var that is cached at the top of testTimingWithDocumentOpen refers to the iframe's original document/contentWindow and once the document.open/write/close occurs, access to that variable is blocked by our script engine.



To avoid the permission denied, if you re-cache the timing var at the start of setTimeout(), the test succeeds in IE9 RC:



  setTimeout(function() {

    var timing = subcontentWindow.performance.timing;

    for (var i in timingAttributes) {

      test_equals(timing[timingAttributes[i]],

                  originalTiming[timingAttributes[i]],

                  timingAttributes[i] + " is the same after document open.");

    }

  }, 0);



The test looks great otherwise.  Thanks for converting it to use an IFRAME.



- Nic



-----Original Message-----
From: public-web-perf-request@w3.org [mailto:public-web-perf-request@w3.org] On Behalf Of Tony Gentilcore
Sent: Wednesday, March 09, 2011 8:55 AM
To: Anderson Quach
Cc: public-web-perf; James Simonsen
Subject: Re: [agenda] Web Performance WG Teleconference #24 Agenda 2011-03-09



> 2.       Tests for Navigation Timing to review.



James updated test_document_open to use a subframe (as we discussed last week). However, in the IE9 RC, it throws a permission denied when calling test_equals(). Anderson or Nic, any ideas?



http://w3c-test.org/webperf/tests/submission/Google/NavigationTiming/test_document_open.htm