Closed
Bug 1217511
Opened 9 years ago
Closed 9 years ago
notificationCallbackMap is not defined
Categories
(WebExtensions :: Untriaged, defect)
WebExtensions
Untriaged
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1203331
People
(Reporter: richardaleon, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/46.0.2490.71 Safari/537.36
Steps to reproduce:
I was attempting to port over a Chrome extension which has notifications with onClosed listeners, and attempted to attach these listeners.
Actual results:
ReferenceError: notificationCallbackMap is not defined. [ext-notifications.js: 131]
The addListener function tries to update notificationCallbackMap, when it is actually initialized as notificationCallback[s]Map.
Expected results:
My notification should have had a callback attached to its onClose event.
Comment 1•9 years ago
|
||
There is no notificationCallbackMap in the Firefox source, and only one match on Google.
Component: Untriaged → WebExtensions
Product: Firefox → Toolkit
Comment 2•9 years ago
|
||
Looks like this should have been fixed by bug 1203331.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
Updated•7 years ago
|
Product: Toolkit → WebExtensions
You need to log in
before you can comment on or make changes to this bug.
Description
•