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
--- 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