Replace all uses of JSWindowActor willDestroy with didDestroy
Categories
(Core :: DOM: Content Processes, task, P2)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox84 | --- | fixed |
People
(Reporter: cpeterson, Assigned: enndeakin)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
What does frontend want from actor lifecycle methods? Can frontend listen for didDestroy in the parent process instead of willDestroy? willDestroy is not reliable.
Should the actor lifecycle methods be changed to mimic web events pageshow/pagehide plus innerwindowdestroy?
| Reporter | ||
Comment 1•5 years ago
|
||
Waiting to hear from Neil Deakin in bug 1649318 which actor fields frontend code uses in willDestroy that aren't available in didDestroy. The DOM Fission team would prefer to remove willDestroy entirely (because it is an unreliable event) in favor of didDestroy.
Updated•5 years ago
|
Updated•5 years ago
|
| Assignee | ||
Comment 2•5 years ago
|
||
Updated•5 years ago
|
| Assignee | ||
Comment 3•5 years ago
|
||
Depends on D90737
Updated•5 years ago
|
Updated•5 years ago
|
| Reporter | ||
Comment 4•5 years ago
|
||
willDestroy will be removed in bug 1662771, so we first need to switch uses of JSWindowActor willDestroy with didDestroy.
Comment 6•5 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/a91e5949ec8f
https://hg.mozilla.org/mozilla-central/rev/2a46f29c8cdd
Description
•