Closed
Bug 1946564
Opened 6 months ago
Closed 5 months ago
Invalidate the about:home startup cache when the New Tab built-in addon detects a pending update
Categories
(Firefox :: New Tab Page, task, P3)
Firefox
New Tab Page
Tracking
()
RESOLVED
FIXED
138 Branch
Tracking | Status | |
---|---|---|
firefox138 | --- | fixed |
People
(Reporter: mconley, Assigned: mconley)
References
(Blocks 1 open bug, Regressed 1 open bug)
Details
(Whiteboard: [hnt-trainhop])
Attachments
(2 files)
The New Tab built-in add-on will not update at runtime. Instead, pending updates will be applied after a restart. We need to ensure that any pre-existing about:home cache is also blown away when an update download is detected (prior to restarting), and prevent any further caching until the next restart.
Updated•6 months ago
|
Assignee | ||
Updated•5 months ago
|
Assignee: nobody → mconley
Assignee | ||
Comment 1•5 months ago
|
||
This also makes it so that we remove the shutdown blocker if we uninit.
Assignee | ||
Comment 2•5 months ago
|
||
Pushed by mconley@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/39bf84ed573e
Part 1: Add AboutHomeStartupCache.clearCacheAndUninit method and test. r=home-newtab-reviewers,nbarrett
https://hg.mozilla.org/integration/autoland/rev/9438672eeffd
Part 2: Call AboutHomeStartupCache.clearCacheAndUninit if the newtab built-in addon gets updated. r=willdurand,home-newtab-reviewers,nbarrett
Comment 4•5 months ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/39bf84ed573e
https://hg.mozilla.org/mozilla-central/rev/9438672eeffd
Status: NEW → RESOLVED
Closed: 5 months ago
status-firefox138:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 138 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•