зеркало из https://github.com/mozilla/gecko-dev.git
42 строки
1.6 KiB
C++
42 строки
1.6 KiB
C++
/* -*- Mode: C++; tab-width: 8; indent-tabs-mode: nil; c-basic-offset: 2 -*- */
|
|
/* vim: set ts=8 sts=2 et sw=2 tw=80: */
|
|
/* This Source Code Form is subject to the terms of the Mozilla Public
|
|
* License, v. 2.0. If a copy of the MPL was not distributed with this
|
|
* file, You can obtain one at http://mozilla.org/MPL/2.0/. */
|
|
|
|
#include "mozilla/dom/ChromeMessageSender.h"
|
|
#include "mozilla/dom/MessageManagerBinding.h"
|
|
|
|
namespace mozilla {
|
|
namespace dom {
|
|
|
|
ChromeMessageSender::ChromeMessageSender(ipc::MessageManagerCallback* aCallback,
|
|
nsFrameMessageManager* aParentManager,
|
|
MessageManagerFlags aFlags)
|
|
: MessageSender(aCallback, aParentManager, aFlags | MessageManagerFlags::MM_CHROME)
|
|
{
|
|
MOZ_ASSERT(!(aFlags & ~(MessageManagerFlags::MM_GLOBAL |
|
|
MessageManagerFlags::MM_PROCESSMANAGER |
|
|
MessageManagerFlags::MM_OWNSCALLBACK)));
|
|
|
|
// This is a bit hackish. We attach to the parent, but only if we have a callback. We
|
|
// don't have a callback for the frame message manager, and for parent process message
|
|
// managers (except the parent in-process message manager). In those cases we wait until
|
|
// the child process is running (see MessageSender::InitWithCallback).
|
|
if (aParentManager && mCallback) {
|
|
aParentManager->AddChildManager(this);
|
|
}
|
|
}
|
|
|
|
JSObject*
|
|
ChromeMessageSender::WrapObject(JSContext* aCx,
|
|
JS::Handle<JSObject*> aGivenProto)
|
|
{
|
|
MOZ_ASSERT(nsContentUtils::IsSystemCaller(aCx));
|
|
|
|
return ChromeMessageSenderBinding::Wrap(aCx, this, aGivenProto);
|
|
}
|
|
|
|
} // namespace dom
|
|
} // namespace mozilla
|