Closed
Bug 1823714
Opened 2 years ago
Closed 1 year ago
Test storage.session is preserved when we restart the extension process, including for non-event pages
Categories
(WebExtensions :: Storage, task, P2)
WebExtensions
Storage
Tracking
(firefox120 fixed)
RESOLVED
FIXED
120 Branch
Tracking | Status | |
---|---|---|
firefox120 | --- | fixed |
People
(Reporter: zombie, Assigned: zombie)
References
(Blocks 2 open bugs, Regressed 1 open bug)
Details
(Whiteboard: [addons-jira])
Attachments
(1 file)
Move the in-memory session storage to the parent process, so that it can survive the extension process getting killed on android.
Add a test that actually kills the extension process.
Updated•2 years ago
|
Updated•2 years ago
|
Severity: -- → N/A
Priority: -- → P2
Assignee | ||
Updated•2 years ago
|
Summary: Move storage.session into the parent process → Test storage.session with killing the extension process
Assignee | ||
Comment 1•1 year ago
|
||
The way we actually landed the implementation made this test less critical, but could still be useful, especially to verify the behavior with persistent background pages is the one we want: namely the storage should still be preserved.
Also adding dev-doc-needed, because this might be surprising behavior (just like most things when we restart a "non-restartless" background page).
Summary: Test storage.session with killing the extension process → Test storage.session is preserved when we restart the extension process, including for non-event pages
Assignee | ||
Comment 2•1 year ago
|
||
Updated•1 year ago
|
Assignee: nobody → tomica
Attachment #9357526 -
Attachment description: WIP: Bug 1823714 - Test storage.session is preserved after extension process crash → Bug 1823714 - Test storage.session is preserved after extension process crash, r?willdurand
Status: NEW → ASSIGNED
Pushed by tjovanovic@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/f2abf2d020f3
Test storage.session is preserved after extension process crash, r=willdurand
Comment 4•1 year ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
status-firefox120:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 120 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•