> Anyway, the good method is not to use AutoConfig, eg not use a simple preference file but a JS script and the function defaultPref(); Ok
That's what AutoConfig is, only you have to specify the location via a prefernce. You have an interesting idea, though. It would be nice if one could have multiple AutoConfig scripts. Maybe I'll implement that. But it would still require the preferences to enable Autoconfig. Firefox does not read AutoConfig files by default. As it stands, though, AutoConfig using pref (not defaultPref) is your best solution for that. And to be clear, pref() in an AutoConfig is totally different than pref() a default Javascript file. The naming is bad. See: https://bugzilla.mozilla.org/show_bug.cgi?id=440908#c30 Mike On Wed, Jun 22, 2016 at 10:57 AM, Marco Gaiarin <[email protected]> wrote: > Mandi! Kaply Consulting > In chel di` si favelave... > > >> I try to explain better: it is a general behaviour, or it is related > >> only to that precise extensions that release also a file in (packed) > >> 'preferences' folder? > > You actually would have this problem with all extensions. > > Ok. ;( > > > >> 2) Adding extension configuration snippet to a single file, and manage > >> it, is a little dumb. > >> There's a code snippet in Autoconfig that can do something like: 'load > >> all .js files in that folder', so i can simply place a .js snippet in > >> some folder (as i was used before packed extensions)? > > In theory, yes. I'm not sure why the packed extensions is making a > difference > > here. > > There's no good way to override any extensions preferences using default > > preferences. You'll always have a race condition. > > Before signing, you could modify the extension directly, but that had > nothing > > to do with packing... > > No, sorry, probably i've explained me badly. > > As sayed, to setup default preferences for some extensions i was used > to simply throw in: > > Mozilla Firefox\browser\defaults\preferences\ > > a preference .js file. You sayed me that probably this method never > worked: i feel the opposite, but probably worked with some old FF > version and simply preference get integrated in user preferences for > old user (and i've never noticed it for new user). > > Anyway, the good method is not to use AutoConfig, eg not use a simple > preference file but a JS script and the function defaultPref(); Ok. > > But Autoconfig get enabled throwing a file in: > > Mozilla Firefox\browser\defaults\preferences\ > > that contains (at least; this is a preference file indeeed, so > preference file get read! why does not work for extensions?): > > pref("general.config.filename", "firefox.cfg"); > pref("general.config.obscure_value", 0); > > then you can use: > > Mozilla Firefox\firefox.cfg > > as an AutoConfig script. Good. > > > There's some way to load not a single AutoConfig script, but a folder > of script; or speaking the same in different way: there's a way to load > in the only AutoConfig script, other autoconfig scripts, better an > entire folder of script (ala debian split-config file)? > > So i can simply put a snippet of AutoConfig file in a folder, and get > sure they work... > > > I hope i was clear now... Thanks. > > -- > dott. Marco Gaiarin GNUPG Key ID: > 240A3D66 > Associazione ``La Nostra Famiglia'' > http://www.lanostrafamiglia.it/ > Polo FVG - Via della Bontà , 7 - 33078 - San Vito al Tagliamento > (PN) > marco.gaiarin(at)lanostrafamiglia.it t +39-0434-842711 f > +39-0434-842797 > > Dona il 5 PER MILLE a LA NOSTRA FAMIGLIA! > http://www.lanostrafamiglia.it/25/index.php/component/k2/item/123 > (cf 00307430132, categoria ONLUS oppure RICERCA SANITARIA) >
_______________________________________________ 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"
