Finalise the design of the search modern configuration WebExtension update mechanisms
Categories
(Firefox :: Search, task, P2)
Tracking
()
People
(Reporter: standard8, Assigned: standard8)
References
Details
We need to allow downloading updated WebExtensions for when we make changes to the configuration.
- The configuration already allows to specify the WebExtensionId and WebExtensionVersion.
- If we detect that the version of the WebExtension is different to that saved on disk, then we should download and apply the new version.
- Once the instance of Firefox has been updated, and we have the new version included, then we should remove the old version.
Ideally, we should aim for minimal disruption to the user - to do that we might have to be clever about how we pass updates to the user, e.g. if a locale name is changing within the WebExtension, we might want to supply one version with both locales for a week or two, then change the config to reference the new one, and at some stage remove the old one.
Assignee | ||
Updated•5 years ago
|
Updated•5 years ago
|
Updated•5 years ago
|
Updated•5 years ago
|
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Updated•5 years ago
|
Updated•5 years ago
|
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 1•5 years ago
|
||
I'm mutating this bug into what we've actually been doing. We looked into the original plan for updating, and found it would cause more an additional route for add-ons to be updated in Firefox. Hence we changed track and have opted to deliver these via Normandy.
The design doc is here: https://docs.google.com/document/d/1dGeZu9NN1B3L2lrbA-yt1nj-8dFWB5-2uY_mg_ThFtY/edit
I'm marking this mutated bug as fixed and will file follow-ups for the work that needs to be done to complete this.
Description
•