Closed Bug 1830337 Opened 5 months ago Closed 5 months ago

Consider to allow builtin colorways pending updates to be applied also when auto-updates are disabled for other add-ons

Categories

(Toolkit :: Add-ons Manager, task, P2)

task
Points:
1

Tracking

()

RESOLVED FIXED
115 Branch
Tracking Status
relnote-firefox --- 115+
firefox115 --- fixed

People

(Reporter: rpl, Assigned: rpl)

References

(Blocks 1 open bug)

Details

(Whiteboard: [addons-jira])

Attachments

(1 file)

As part of allowing clients with a colorway builtin theme set to keep the colorway theme when we will remove them from the Gecko builds, we need to account that some clients may have extensions.update.autoUpdateDefault set to false, in which case Gecko still checks for add-on updates in the background but the updates found will be kept pending until the user will explicitly apply them (unlike extensions.update.enabled which would disable also checking for updates).

The users are not being notified when an add-on update has been found in the background and so the users would not be aware of the pending update unless the about:addons tab is explicitly open.

This bug is tracking considering to special case pending updates specifically for the colorway builtin theme being migrated (and instead keep the current expected behavior for any other add-on, included colorway theme that have been migrated to the AMO-hosted xpi file and installed in the user profile).

Blocks: 1815898
Assignee: nobody → lgreco
Status: NEW → ASSIGNED
Severity: -- → S3
Priority: -- → P2

There is an r+ patch which didn't land and no activity in this bug for 2 weeks.
:rpl, could you have a look please?
If you still have some work to do, you can add an action "Plan Changes" in Phabricator.
For more information, please visit BugBot documentation.

Flags: needinfo?(wdurand)
Flags: needinfo?(lgreco)
Pushed by luca.greco@alcacoop.it:
https://hg.mozilla.org/integration/autoland/rev/2f57e657f378
Allow builtin colorways pending updates to be applied also when auto-updates are disabled for other add-ons. r=willdurand
Flags: needinfo?(wdurand)
Flags: needinfo?(lgreco)
Status: ASSIGNED → RESOLVED
Closed: 5 months ago
Resolution: --- → FIXED
Target Milestone: --- → 115 Branch

Release Note Request (optional, but appreciated)
[Why is this notable]:

  • To preserve the user choice related to the colorway builtin theme selected, in Firefox 115 we will be exempting the colorway builtin update (converting the builtin into a profile installed theme) from honoring the extensions.update.autoUpdateDefault pref when set to false (which prevents addons updates found from being auto-applied and keeps them pending)
  • without this change, when the colorways builtin themes will be removed from the Firefox builds, the users with extensions.update.autoUpdateDefault pref set to false would lose their colorway theme and be switched automatically to the default theme.
    [Affects Firefox for Android]: No

[Suggested wording]: To prevent user data loss, retained Firefox Colorways built-in themes will be automatically migrated to the same Colorways themes hosted on addons.mozilla.org for Firefox profiles that have add-ons auto-updates disabled.
[Links (documentation, blog post, etc)]: No

relnote-firefox: --- → ?

:luca thanks for the nomination, could you give me some suggested wording for this? Something I can start from to create a release note.

Flags: needinfo?(lgreco)

(In reply to Donal Meehan [:dmeehan] from comment #6)

:luca thanks for the nomination, could you give me some suggested wording for this? Something I can start from to create a release note.

I have just updated comment 5 with some suggested wording.

Flags: needinfo?(lgreco)

Thanks, added a slightly reworded note to the Nightly release notes. Keeping the relnote? flag open to keep it on the radar for inclusion in our final release notes.

You need to log in before you can comment on or make changes to this bug.