Test for form submission targeting remote frame.

components/test_runner/test_runner.cc

Index: components/test_runner/test_runner.cc
diff --git a/components/test_runner/test_runner.cc b/components/test_runner/test_runner.cc
index 1a6aa90e4561740cd7beba026cc70f6f4ad1b3d5..a3e6b7ab68151905bfc82d43a0251c48409c2da1 100644
--- a/components/test_runner/test_runner.cc
+++ b/components/test_runner/test_runner.cc
@@ -1928,9 +1928,6 @@ class WorkItemBackForward : public TestRunner::WorkItem {
 };
 
 void TestRunner::NotifyDone() {
-  // Test didn't timeout. Kill the pending callbacks.
-  weak_factory_.InvalidateWeakPtrs();

[Łukasz Anforowicz, 2016/05/19 23:01:16]

If I don't remove this, then calling testRunner.notifyDone() will invalidate
TestRunner's weak pointers and therefore will invalidate all TestRunner-specific
bindings held by TestRunnerBindings.  This undesirable behavior of
testRunner.notifyDone was introduced in
https://codereview.chromium.org/1852603002 which got rid of
TestRunner::task_list_ and reused TestRunner::weak_factory_ for cancellation of
callbacks.

I think it is fine to remove this call, because everything will still be
cleaned-up before the next test, because we call
weak_factory_.InvalidateWeakPtrs() from TestRunner::Reset.

One could argue that we might want to still cancel pending callbacks, to avoid
any activity while BlinkTestRunner is working on creating the final test dump
(text, pixel, etc.).  To accomplish this, we might move the
weak_factory_.InvalidateWeakPtrs() call into *Complete*NotifyDone method, right
before it calls delegate_->TestFinished().  I think this would be a wrong thing
to do because it wouldn't really help: it wouldn't stop *future* callbacks (i.e.
using weak pointers obtained in the future, before the next call to
TestRunner::Reset).  Since doing this wouldn't really help, let's just not add
this extra complexity.

I do note that all the tests pass without the removed code.

Sounds good?

-
   CompleteNotifyDone();
 }