On Fri, Mar 16, 2018 at 8:53 AM, James Pearson <[email protected]> wrote:
> Mike Kaply wrote: > > > >> So, i see moving to a JSON policies file as a step down from having a > >> JS engine in 'mozilla.cfg'/autoconfig. Am i missing something? > > > > If you've been using Autoconfig since the early days, you probably > > only use lockPref/pref/defaultPref, so you have nothing to worry > > about. Any changes we make to Autoconfig are about removing the fact > > that it was accidentally changed at some point to allow access to > > system globals. > > The bit about 'removing access to system globals' worries me - we set up > a couple of custom protocol handlers in our AutoConfig cfg > > We also enable a local copy of the 'OpenH264 Video Codec' via the > AutoConfig cfg - as most of our users don't have access to the Internet. > We use this with an in-house video chat system > > Does this mean we may not be able to do this in the future? > Only on Rapid Release, not on ESR. I'd like to investigate adding protocol handlers to the policy manager. I would need more details on how you're adding the codec. Mike > > Thanks > > James Pearson
_______________________________________________ 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"
