Notify to the WebExtensions internals when extension background service workers are being spawned or terminated
Categories
(WebExtensions :: General, task, P1)
Tracking
(firefox96 fixed)
Tracking | Status | |
---|---|---|
firefox96 | --- | fixed |
People
(Reporter: rpl, Assigned: rpl)
References
(Blocks 1 open bug)
Details
(Whiteboard: [mv3-m2])
Attachments
(10 files)
(deleted),
text/x-phabricator-request
|
Details | |
(deleted),
text/x-phabricator-request
|
Details | |
(deleted),
text/x-phabricator-request
|
Details | |
(deleted),
text/x-phabricator-request
|
Details | |
(deleted),
text/x-phabricator-request
|
Details | |
(deleted),
text/x-phabricator-request
|
Details | |
(deleted),
text/x-phabricator-request
|
Details | |
(deleted),
text/x-phabricator-request
|
Details | |
(deleted),
text/x-phabricator-request
|
Details | |
(deleted),
text/x-phabricator-request
|
Details |
As a follow up to Bug 1688040, the WebExtensions internals running in the extension process should be notified when an extension background service workers are being spawned or terminated, similarly to how we are being notified for the extension windows being created and destroyed.
Updated•3 years ago
|
Assignee | ||
Comment 1•3 years ago
|
||
Assignee | ||
Comment 2•3 years ago
|
||
Depends on D124697
Assignee | ||
Comment 3•3 years ago
|
||
Depends on D124698
Assignee | ||
Comment 4•3 years ago
|
||
Depends on D124699
Assignee | ||
Comment 5•3 years ago
|
||
Depends on D124700
Assignee | ||
Comment 6•3 years ago
|
||
Depends on D124701
Assignee | ||
Comment 7•3 years ago
|
||
Depends on D124702
Assignee | ||
Comment 8•3 years ago
|
||
Depends on D124703
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Assignee | ||
Comment 9•3 years ago
|
||
Depends on D124704
Assignee | ||
Comment 10•3 years ago
|
||
Depends on D124782
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Updated•3 years ago
|
Comment 11•3 years ago
|
||
Comment 12•3 years ago
|
||
Backed out 10 changesets (Bug 1728326) for causing build bustages.
Backout link
Push with failures
Failure Log
Assignee | ||
Comment 13•3 years ago
|
||
My apologies, I actually fixed that same debug build failure in a couple of the patches attached to this bug but apparently D124701 was missing one that I had locally.
And so my push to try was successfully completing the debug build, but the ones pushed from Lando could not without that trivial change my push to try already had.
I just updated D124701 (along with updating also the other ones that were likely already updated, just in case I missed another one), and will push to autoland again shortly.
Comment 14•3 years ago
|
||
Comment 15•3 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/0b0479a00c80
https://hg.mozilla.org/mozilla-central/rev/cc488a5fabad
https://hg.mozilla.org/mozilla-central/rev/afb346a9eb0a
https://hg.mozilla.org/mozilla-central/rev/e5db0d655a19
https://hg.mozilla.org/mozilla-central/rev/83e0401fe863
https://hg.mozilla.org/mozilla-central/rev/29639f9f4696
https://hg.mozilla.org/mozilla-central/rev/61f6df514baf
https://hg.mozilla.org/mozilla-central/rev/73e1ee1385ed
https://hg.mozilla.org/mozilla-central/rev/1201687418dc
https://hg.mozilla.org/mozilla-central/rev/eed6f4952eb0
Description
•