On 7/15/2016 5:09 AM, [email protected] wrote:
Based on the last assumption, not really, you could always do a condition based on a preference that is set per user.Good thing is you then have some "version control" on when new settings need to be pushed out once per user profile, all you need to do is push out a change to the AutoConfig file and the next time the user launches FF it will set the preferences. Here is short example typed out of the head so you get an idea of how you could do this, you might need to adapt some things if you've been locking down prefs etc etc. You probably get the idea! ;) Be sure to do a thorough test before running in production! // Check if a preference is set to the correct value if (getPref("internalcompany.app.update.enabled") != "1.0") { // Change the setting pref("app.update.enabled", false); // Update the preference to the correct value so it doesn't run on next start pref("internalcompany.app.update.enabled ", "1.0"); }
Thank you , I may give this a try. _______________________________________________ Enterprise mailing list [email protected] https://mail.mozilla.org/listinfo/enterprise To unsubscribe from this list, please visit https://mail.mozilla.org/listinfo/enterprise or send an email to [email protected] with a subject of "unsubscribe"
