Bug 754202 - Fix content->chrome postMessage mochitest. r=bz

This isn't something we actually support, and were using enablePrivilege to do it before.
When we switch this to SpecialPowers wrapping, the sender origin becomes a chrome URL (not
very interesting) and the source window becomes null (which we do explicitly in
nsGlobalWindow for chrome callers). So those tests stop being useful.
This commit is contained in:
Bobby Holley 2012-06-07 14:28:21 +02:00
parent 9bdcc2117b
commit 09834cc4d8
2 changed files with 1 additions and 7 deletions

View File

@ -37,9 +37,7 @@
function respond(msg)
{
// ...so get privileges and test that this works with privileges
netscape.security.PrivilegeManager.enablePrivilege("UniversalXPConnect");
window.parent.postMessage(msg, "*");
SpecialPowers.wrap(window).parent.postMessage(msg, "*");
}
window.addEventListener("message", receiveMessage, false);

View File

@ -93,10 +93,6 @@ function chromePathIsSet(evt)
function receiveContent(evt)
{
is(evt.isTrusted, true, "should have sent a trusted event");
is(evt.origin, "http://example.org", "content response event has wrong URI");
is(evt.source, window.frames.contentDomain,
"wrong source for same-domain message!");
finish();
}