summaryrefslogtreecommitdiffstats
path: root/dom/push/PushComponents.sys.mjs
diff options
context:
space:
mode:
Diffstat (limited to 'dom/push/PushComponents.sys.mjs')
-rw-r--r--dom/push/PushComponents.sys.mjs12
1 files changed, 6 insertions, 6 deletions
diff --git a/dom/push/PushComponents.sys.mjs b/dom/push/PushComponents.sys.mjs
index 0ad0505851..4a2bfc1279 100644
--- a/dom/push/PushComponents.sys.mjs
+++ b/dom/push/PushComponents.sys.mjs
@@ -40,7 +40,7 @@ const OBSERVER_TOPIC_SUBSCRIPTION_MODIFIED = "push-subscription-modified";
* similar to the Push DOM API, but does not require service workers.
*
* Push service methods may be called from the parent or content process. The
- * parent process implementation loads `PushService.jsm` at app startup, and
+ * parent process implementation loads `PushService.sys.mjs` at app startup, and
* calls its methods directly. The content implementation forwards calls to
* the parent Push service via IPC.
*
@@ -78,7 +78,7 @@ PushServiceBase.prototype = {
return this._messages.includes(message.name);
},
- observe(subject, topic, data) {
+ observe(subject, topic) {
if (topic === "android-push-service") {
// Load PushService immediately.
this.ensureReady();
@@ -102,7 +102,7 @@ PushServiceBase.prototype = {
/**
* The parent process implementation of `nsIPushService`. This version loads
- * `PushService.jsm` at startup and calls its methods directly. It also
+ * `PushService.sys.mjs` at startup and calls its methods directly. It also
* receives and responds to requests from the content process.
*/
let parentInstance;
@@ -165,7 +165,7 @@ Object.assign(PushServiceParent.prototype, {
result => {
callback.onUnsubscribe(Cr.NS_OK, result);
},
- error => {
+ () => {
callback.onUnsubscribe(Cr.NS_ERROR_FAILURE, false);
}
)
@@ -192,10 +192,10 @@ Object.assign(PushServiceParent.prototype, {
domain,
})
.then(
- result => {
+ () => {
callback.onClear(Cr.NS_OK);
},
- error => {
+ () => {
callback.onClear(Cr.NS_ERROR_FAILURE);
}
)