Closed
Bug 1823436
Opened 2 years ago
Closed 1 year ago
Evaluate Android compatibility with non-persistent background scripts
Categories
(GeckoView :: Extensions, task, P3)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: calu, Unassigned)
References
(Depends on 1 open bug)
Details
(Whiteboard: [fxdroid] [foundation])
An event page is like a background page, but non-persistent. The internals of GV (and consumers such as A-C/Fenix?) should be audited, to see if there is anything that assumes the extension to be alive forever. They should not assume that, because event pages codify that the background scripts of extensions can be terminates/resumed during the extension's lifetime, by design.
|
Reporter | |
Updated•2 years ago
|
Severity: -- → N/A
Priority: -- → P3
Whiteboard: [addons-jira] [fxdroid] [foundation]
|
||
Updated•2 years ago
|
|
||
Updated•2 years ago
|
Whiteboard: [addons-jira] [fxdroid] [foundation] → [fxdroid] [foundation]
|
|
||
Updated•2 years ago
|
|
||
Comment 1•1 year ago
|
||
- bug 1853013 migrated webcompat add-on to event pages.
- bug 1826244 about Firefox Accounts WebChannel (depends on bug 1823432).
- Marked as resolved, but has not been migrated to event pages...?
- bug 1826245 ReaderView migrated to event pages.
- webcompat reporter is still using persistent background pages. There was an attempt to migrate it, but it got backed out for unrelated reasons (https://bugzilla.mozilla.org/show_bug.cgi?id=1852340#c32).
- We can either retry migrating it to an event page, or replace the add-on component (bug 1879606).
There are no other built-in extensions in Fenix, Android-Components or Gecko/GeckoView.
|
|
||
Comment 2•1 year ago
|
||
The assessment of the work to be done has been completed, the remaining work is tracked in separate bugs:
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•