Bug 1261842 - browser_async_window_flushing.js no longer needs to wait for remoteness flip on initial browser of new window. r?felipe draft
authorMike Conley <mconley@mozilla.com>
Wed, 08 Jun 2016 16:22:13 -0400
changeset 392007 086fe0d339c1f1aaec828f95a7d242010c067375
parent 392006 a20e3d6d846a20f47533b6f5dfcd10da068c03fa
child 392008 cb6234559ae0a1ea2e32bd901235ad4aa5373f6c
push id23919
push usermconley@mozilla.com
push dateFri, 22 Jul 2016 20:54:03 +0000
reviewersfelipe
bugs1261842
milestone50.0a1
Bug 1261842 - browser_async_window_flushing.js no longer needs to wait for remoteness flip on initial browser of new window. r?felipe MozReview-Commit-ID: E74rDTQ2FjX
browser/components/sessionstore/test/browser_async_window_flushing.js
--- a/browser/components/sessionstore/test/browser_async_window_flushing.js
+++ b/browser/components/sessionstore/test/browser_async_window_flushing.js
@@ -31,25 +31,16 @@ add_task(function* test_add_interesting_
 
   // Send a message that will cause the content to change its location
   // to someplace more interesting. We've disabled auto updates from
   // the browser, so the parent won't know about this
   yield ContentTask.spawn(browser, PAGE, function*(PAGE) {
     content.location = PAGE;
   });
 
-  // for e10s, this will cause a remoteness switch, since the
-  // initial browser in a newly opened window will not be remote.
-  // We need to wait for that remoteness change before we attach
-  // our OnHistoryReplaceEntry listener.
-  if (gMultiProcessBrowser) {
-    yield BrowserTestUtils.waitForEvent(newWin.gBrowser.selectedTab,
-                                        "TabRemotenessChange");
-  }
-
   yield promiseContentMessage(browser, "ss-test:OnHistoryReplaceEntry");
 
   // Clear out the userTypedValue so that the new window looks like
   // it's really not worth restoring.
   browser.userTypedValue = null;
 
   // Once the domWindowClosed Promise resolves, the window should
   // have closed, and SessionStore's onClose handler should have just