Closed
Bug 1368830
Opened 9 years ago
Closed 8 years ago
port.onDisconnect not firing in content script when addon is shutdown/upgraded
Categories
(WebExtensions :: Untriaged, defect, P5)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1223425
People
(Reporter: noitidart, Unassigned)
Details
(Whiteboard: triaged)
1) Create a content script.
2) Connect to runtime with:
const port = extension.runtime.connect({ name:'myport' });
3) Add disconnect listener
port.onDisconnect.addListener(function() {
console.log('port disconnected! either background script did port.disconnect() OR addon shutdown/upgraded');
});
Expected behavior:
In Chrome this fires the onDisconnect.
Actual behavior:
In Firefox and Edge it does not trigger on addon shutdown/upgrade. It only triggers if background script calls port.disconnect().
Component: Untriaged → WebExtensions: Untriaged
Product: Firefox → Toolkit
|
||
Updated•9 years ago
|
Priority: -- → P5
Whiteboard: triaged
|
||
Comment 1•8 years ago
|
||
Duplicate of bug 1223425?
Thanks @Shell and @Chris - I closed this as duplicate of bug 1223425.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
|
||
Updated•8 years ago
|
Product: Toolkit → WebExtensions
You need to log in
before you can comment on or make changes to this bug.
Description
•