Mike Kaply wrote: > >>> We're trying to get everything, but there might be some little used >>> things that don't make it in the first pass. >> >> Any ideas at this point of the things that won't make the first pass? > > Not yet. We have a general concept of an MVP, but once we have a beta if > there are > things that are not there that folks need, we can still get them in. > > Also we have permission to do policy work on the ESR, so it won't be > "no policy changes until the next ESR"
That is good to know ... >> For example, we have a couple of third party extensions we install for >> all users - and we set relevant prefs for these extensions via the >> Autoconfig ... >> >> So I would guess that you would probably have to support arbitrary >> preferences via Policies ? > > That would be an example of why to keep Autoconfig :) > > But that won't work post 57 anyway because WebExtensions can't read > preferences... > > If an extension needs a way to read external preferences, it will have to use > something like storage.managed. There's really no way to preset preferences > for an extension. OK - I hadn't appreciated that WebExtensions can't read preferences - which is something we will have to think about .. >> That said, I for one, would hope (actually, require) that Autoconfig >> will still exist - as I use it for more than just setting prefs and >> using CCK2 > > It will probably still exist, but it will be sandboxed back to the original > API so it can be used as intended. Not sure what you mean by 'sandboxed back to the original API' ... What was the original API? - and does that mean there will be things that we won't be able to do with Autoconfig files? 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"
