Add pref default for automatic vs. ask-me add-on update

RESOLVED FIXED in seamonkey2.1b3

Status

SeaMonkey
Preferences
--
enhancement
RESOLVED FIXED
7 years ago
7 years ago

People

(Reporter: tonymec, Assigned: rsx11m)

Tracking

Trunk
seamonkey2.1b3
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [AddonsRewriteTestday][AddonsRewrite])

Attachments

(1 attachment)

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.3a5pre) Gecko/20100610 SeaMonkey/2.1a2pre

(Maybe wait until bug 562622 will have landed) Add pref in "Edit => Preferences => Advanced => Software Installation" to switch all extensions from "Update automatically" to "Ask me" or vice-versa, similarly to what is already done for SeaMonkey. This is the SeaMonkey counterpart (or maybe a complement) of bug 562622 comment #4 point 2 (IMHO in SeaMonkey the UI should exist not only in the new add-on manager (which hasn't got it yet) but also next to where very closely related prefs live in SeaMonkey's Preferences.
Status: UNCONFIRMED → NEW
Ever confirmed: true
QA Contact: add-ons.manager → preferences
Assignee: nobody → bugspam.Callek
Blocks: 561600
Depends on: 586574
The minimum is to simply add the new extensions.update.autoUpdateDefault pref to browser-prefs.js.

Comment 2

7 years ago
For the UI, the new add-ons manager now has it, but it might be a good idea to reorganizer the updates sections of the software installation prefs dialog into application and add-ons groups, and make the add-ons group have that pref as well.
(In reply to comment #2)
> For the UI, the new add-ons manager now has it, but it might be a good idea to
> reorganizer the updates sections of the software installation prefs dialog into
> application and add-ons groups, and make the add-ons group have that pref as
> well.


Neil, [as ui tsar] do you have a preference on if and where we expose this pref in our UI?

I'm partial to only in addon manager itself, (or that plus update pane of prefwindow) but whatever you choose, we can get it done.

Comment 4

7 years ago
I wondered a bit, but I think what bug 595744 removes from the add-on manager itself isn't the "update automatically" pref but just one to search for them...

Comment 5

7 years ago
So this new pref is the addon counterpart to the app.update.auto pref? If so then yes I think it would be reasonable to add it to the Software Update pane. You'd probably need to reorganise the pane a bit though.
(Assignee)

Comment 6

7 years ago
Is this bug still applicable after the bug 606482 redesign of that pane?

  [ ] Allow websites to install add-ons and updates
      [ ] Automatically check for updates ( ) daily ( ) weekly
          [ ] Automatically download and install the updates

The last option seems to be what's asked for here.
As you can see from looking at pref-smartupdate.xul, we now have all relevant extensions.update.* prefs in the UI. What's missing is what I wrote in comment 1: We have only have .enabled, .url and .interval in browser-prefs.js, but not yet .autoUpdateDefault. Cf. http://mxr.mozilla.org/comm-central/source/mozilla/browser/app/profile/firefox.js#76 (haven't checked in the back-end what the default is, but I for one think it's bad to have something in the UI but not about:config).

Go for it!
(Assignee)

Comment 8

7 years ago
Searching for it in toolkit appears to confirm that a backend is present for the extensions.update.autoUpdateDefault preference, thus the only item left is to set a default value in suite/browser/browser-prefs.js matching Firefox's?
(In reply to comment #8)
> Searching for it in toolkit appears to confirm that a backend is present for
> the extensions.update.autoUpdateDefault preference, thus the only item left is
> to set a default value in suite/browser/browser-prefs.js matching Firefox's?

Yes, as I had guessed and confirmed now, the Add-on Manager back-end ensures the pref is true by default, but we should really provide a default pref in browser-prefs.js to have consistency between UI and about:config.
(Assignee)

Comment 10

7 years ago
Looking at bug 586574 which implemented that preference, it is not clear to me if there is an "extensions.{GUID}.update.autoUpdateDefault" override of the default for specific extensions as well. If yes, it can probably go along with the ".{enabled,url,interval}" prefs, otherwise it should be rather separate.
(Assignee)

Updated

7 years ago
Assignee: bugspam.Callek → rsx11m.pub
OS: Linux → All
Hardware: x86 → All
Summary: Add pref for auto vs. ask-me addon update → Add pref default for automatic vs. ask-me add-on update
(In reply to comment #10)
> Looking at bug 586574 which implemented that preference, it is not clear to me
> if there is an "extensions.{GUID}.update.autoUpdateDefault" override of the
> default for specific extensions as well. If yes, it can probably go along with
> the ".{enabled,url,interval}" prefs, otherwise it should be rather separate.
The {GUID} is a placeholder. The actual GUID depends on the extension. So for instance, if you wanted to stop automatically updating the debugQA extension, you could set extensions.debugQA@mozilla.org.update.autoUpdateDefault to true.
(In reply to comment #8)
> Searching for it in toolkit appears to confirm that a backend is present for
> the extensions.update.autoUpdateDefault preference, thus the only item left is
> to set a default value in suite/browser/browser-prefs.js matching Firefox's?

Correct.
(Assignee)

Comment 13

7 years ago
Created attachment 519381 [details] [diff] [review]
Proposed patch [Checkin: comment 16]

Thanks for the input. I've added the pref to the {GUID} block per comment #11. The Software Installation settings now show "Automatically download and install the updates" correctly checked by default with a new profile. This patch also tries to improve the inline comments of the preferences a bit.
Attachment #519381 - Flags: review?(neil)
Comment on attachment 519381 [details] [diff] [review]
Proposed patch [Checkin: comment 16]

Hmm, well I don't know what they mean by "symmetric" here but it looks OK.
Attachment #519381 - Flags: review?(neil) → review+
(Assignee)

Comment 15

7 years ago
Yeah, I was a bit confused by that too, but I figured that whoever wrote it that way had an idea how it's called, thus didn't touch it.  ;-)

Thanks for the quick review, push for comm-central please.
Keywords: checkin-needed
(Assignee)

Updated

7 years ago
Blocks: 641252
Depends on: 606482
Comment on attachment 519381 [details] [diff] [review]
Proposed patch [Checkin: comment 16]

http://hg.mozilla.org/comm-central/rev/063b5457a683
Attachment #519381 - Attachment description: Proposed patch → Proposed patch [Checkin: comment 16]
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Keywords: checkin-needed
Resolution: --- → FIXED
Target Milestone: --- → seamonkey2.1b3
You need to log in before you can comment on or make changes to this bug.