Closed
Bug 1359195
Opened 7 years ago
Closed 7 years ago
Log spam: JavaScript error: resource:///modules/ExtensionPopups.jsm, line 120: Error: Popup destroyed
Categories
(WebExtensions :: General, defect, P3)
WebExtensions
General
Tracking
(firefox55 affected)
RESOLVED
DUPLICATE
of bug 1341947
Tracking | Status | |
---|---|---|
firefox55 | --- | affected |
People
(Reporter: Gijs, Unassigned)
Details
(Whiteboard: [triaged])
I see a lot of these: Log spam: JavaScript error: resource:///modules/ExtensionPopups.jsm, line 120: Error: Popup destroyed when opening the overflow panel (after resizing my window to be narrow) in my regular dev profile and hovering around. It seems to be caused by the webextensions add-on that's in the overflow panel, as I don't see this on a clean profile.
Reporter | ||
Comment 1•7 years ago
|
||
(In reply to :Gijs from comment #0) > Log spam: JavaScript error: resource:///modules/ExtensionPopups.jsm, line > 120: Error: Popup destroyed Err, slightly too quick with the copy-paste from the summary there - I see that line without the "Log spam: " prefix, of course...
Updated•7 years ago
|
status-firefox55:
--- → affected
status-firefox57:
affected → ---
Updated•7 years ago
|
Priority: -- → P3
Whiteboard: [triaged]
Also, don't know what's meant by overflow panel? I click nothing and this event is fired once after each mouse out from browser's action button icon with a popup defined. As I'm developing a WebExtension based add-on, I am running the web-ext command, which creates a clean profile on every use. The error occurs regardless. If I do not define a popup anywhere, either in manifest.json or in a background script with browser.browserAction.setPopup(), then I do not receive the error. Even if I use only a plain html popup (link and script tags commented out), I receive the error. Even if the browser is maximixed, taking up most of the screen, or made very narrow, I receive the error.
Reporter | ||
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
Updated•6 years ago
|
Product: Toolkit → WebExtensions
You need to log in
before you can comment on or make changes to this bug.
Description
•