Bug 1489301 - Part 3: Fix test expecting interfaces not exposed on System, r=bzbarsky

The `Window` interface is now exposed on system globals, so the check is now
invalid.

Differential Revision: https://phabricator.services.mozilla.com/D9403
This commit is contained in:
Nika Layzell 2018-10-22 10:03:52 -04:00
Родитель 91cec0e775
Коммит 7367cf400e
1 изменённых файлов: 2 добавлений и 2 удалений

Просмотреть файл

@ -32,7 +32,7 @@ https://bugzilla.mozilla.org/show_bug.cgi?id=1139964
ppm.removeMessageListener(msgName, processListener);
ok(m.data.hasPromise, "ProcessGlobal should have Promise object in the global scope!");
ok(m.data.hasTextEncoder, "ProcessGlobal should have TextEncoder object in the global scope!");
ok(!m.data.hasWindow, "ProcessGlobal should not have Window object in the global scope!");
ok(m.data.hasWindow, "ProcessGlobal should have Window object in the global scope!");
messageManager.addMessageListener(msgName, tabListener)
messageManager.loadFrameScript("data:,(" + mmScriptForPromiseTest.toString() + ")()", true);
@ -42,7 +42,7 @@ https://bugzilla.mozilla.org/show_bug.cgi?id=1139964
messageManager.removeMessageListener(msgName, tabListener);
ok(m.data.hasPromise, "TabChildGlobal should have Promise object in the global scope!");
ok(m.data.hasTextEncoder, "TabChildGlobal should have TextEncoder object in the global scope!");
ok(!m.data.hasWindow, "TabChildGlobal should not have Window object in the global scope!");
ok(m.data.hasWindow, "TabChildGlobal should have Window object in the global scope!");
opener.setTimeout("done()", 0);
window.close();