Null out LocalDOMWindow::m_frame on navigation.

third_party/WebKit/LayoutTests/http/tests/security/frameNavigation/resources/popup-ready-to-navigate-child.html

Index: third_party/WebKit/LayoutTests/http/tests/security/frameNavigation/resources/popup-ready-to-navigate-child.html
diff --git a/third_party/WebKit/LayoutTests/http/tests/security/frameNavigation/resources/popup-ready-to-navigate-child.html b/third_party/WebKit/LayoutTests/http/tests/security/frameNavigation/resources/popup-ready-to-navigate-child.html
index d8d38784fa059af2feb16f399437fcfeb76f885b..ed94e48a9510e708d46238790b8b468827d10588 100644
--- a/third_party/WebKit/LayoutTests/http/tests/security/frameNavigation/resources/popup-ready-to-navigate-child.html
+++ b/third_party/WebKit/LayoutTests/http/tests/security/frameNavigation/resources/popup-ready-to-navigate-child.html
@@ -1,6 +1,7 @@
 <script>
+var f = window.frames;
 function go() {
-    window.frames[0].location = "http://127.0.0.1:8000/security/frameNavigation/resources/fail.html";
+    f[0].location = "http://127.0.0.1:8000/security/frameNavigation/resources/fail.html";

[dcheng, 2015/09/29 07:53:25]

Incidentally... this test was actually failing when run manually without my
changes.

+japhet... is there any DRT callback to dump out loading attempts? 

Alternatively, maybe using a JS URL to try to alert here would be good enough?

[Nate Chapin, 2015/09/29 21:49:00]

How was it failing? There's a DRT mode that will dump resource messages, but I
don't see that in use for any users of this file.

[dcheng, 2015/09/29 21:53:52]

I believe this test is attempting to test that this navigation is blocked. Since
there's no event to listen to in this circumstance, the test just completes and
optimistically hopes that the navigation wasn't scheduled.

However, if you ran it locally, it did navigate to fail.html and pop up an
alert().

 }
 opener.postMessage("ready", "*");
 </script>