WebExt API: Add browser.experiments.urlbar.isBrowserUpdateReadyToInstall call
Categories
(Firefox :: Address Bar, enhancement, P2)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox72 | --- | fixed |
People
(Reporter: bugzilla, Assigned: mak)
References
Details
Attachments
(1 file)
|
(deleted),
text/x-phabricator-request
|
Details |
This checks for available update and would usually be used in tandem with browser.app.updateBrowser.
See appUpdater.isApplied(); appUpdater.isPending(); appUpdater.isDownloading(); appUpdater.updateDisabledByPolicy().
|
||
Updated•5 years ago
|
|
||
Updated•5 years ago
|
|
|
||
Updated•5 years ago
|
|
|
||
Updated•5 years ago
|
|
|
||
Updated•5 years ago
|
|
Assignee | |
Comment 1•5 years ago
|
||
I'm changing the API to isUpdateReadyToInstall, because that's what the mock-up shows. We should not start an update check, we should just point out that an update is already pending or applied, afaict (the text states "is downloaded and ready to install").
|
|
Assignee | |
Comment 2•5 years ago
|
||
My understanding is that the add-on will check isUpdateReadyToInstall, if it's true it will show the intervention asking to apply the update (Bug 1579935)
|
|
Assignee | |
Comment 3•5 years ago
|
||
|
|
||
Comment 4•5 years ago
|
||
(In reply to Marco Bonardo [:mak] from comment #2)
My understanding is that the add-on will check isUpdateReadyToInstall, if it's true it will show the intervention asking to apply the update
Yes. Taking a closer look, there are a few things we need according to the Scenarios section under Update Intervention in this doc: https://docs.google.com/document/d/1pN0y8TkadgeQHF3k-t-sPDWHkfXTyno7tjAQf-IUtU0/edit#heading=h.j3x1nhpkzmqv
- Need to know whether an update is staged (this bug)
- If an update is staged, need to be able to restart the browser
- If an update isn't staged, need to know whether the user is on the latest version
Bug 1579935 is about updateBrowser, but it really should be about point 2, restarting the browser. I'll comment there.
We don't have a bug for point 3. I'm not sure whether it's even possible, but I'll file a bug. We may need to fall back to the "Get the latest Firefox browser" fallback in the doc linked above.
|
|
||
Comment 5•5 years ago
|
||
|
||
Updated•5 years ago
|
|
|
Assignee | |
Updated•5 years ago
|
|
||
Comment 7•5 years ago
|
||
| bugherder | ||
Description
•