Bug 1325814 - Clarify file overview comment in ExtensionChild.jsm
At its inception, ExtensionChild.jsm was meant to be used for the
extension child process. Over time, this intent was not consistently
followed, and in
bug 1317697 this was fixed by splitting some logic
in ExtensionChild.jsm off to ExtensionPageChild.jsm.
Henceforth ExtensionChild.jsm handles logic that is common to all
content processes, including web content and extension logic.
Updated the comment at the top of the file to match this reality.
MozReview-Commit-ID: 3cAd0FPj6Vz
--- a/toolkit/components/extensions/ExtensionChild.jsm
+++ b/toolkit/components/extensions/ExtensionChild.jsm
@@ -4,20 +4,19 @@
* 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/. */
"use strict";
/* exported ExtensionChild */
var EXPORTED_SYMBOLS = ["ExtensionChild"];
-/*
- * This file handles addon logic that is independent of the chrome process.
- * When addons run out-of-process, this is the main entry point.
- * Its primary function is managing addon globals.
+/**
+ * This file handles addon logic that is independent of the chrome process and
+ * may run in all web content and extension processes.
*
* Don't put contentscript logic here, use ExtensionContent.jsm instead.
*/
ChromeUtils.import("resource://gre/modules/Services.jsm");
ChromeUtils.import("resource://gre/modules/XPCOMUtils.jsm");
XPCOMUtils.defineLazyServiceGetter(this, "finalizationService",