worldfor.blogg.se - Downgrade to firefox 56

We are working on better support for macOS and Linux.

We are continuing to update the policy code to bring it as close as we can to CCK2 functionality.

As we implement policies, they will be uplifted into the next minor ESR update. You will not be stuck with the existing implementation until the next major ESR.

Updates to the policy code and additional policies are being allowed on the ESR.

If you find bugs or have feature requests, please report them on Github or in Bugzilla.Ī couple other notes that might be useful:

There’s a possibility that some of these methods might not work in the future, so we’d like to find out now what we need to do to make things working. If you find things that you are not able to do with the policy engine, please let us know. Please investigate using the new policy manager to replace any method you’ve used in the past, including the distribution directory, AutoConfig and CCK2. So, I want to take a moment to encourage everyone:

As a result, I know there are many installations of Firefox that use methods that are definitely not recommended anymore, especially now that we have real policy support. I’m absolutely ecstatic that Mozilla decided that adding support for enterprise features was important.īut I have to admit something over the years in my zeal to get enterprise support into Firefox, I’ve encouraged just about every method possible to get customizations into Firefox. So, to say that I’m happy about this particular release would be an understatement. The first version of the CCK Wizard was released on and was for Firefox 1.5 My first post about Firefox in the enterprise was published on Maand was about Firefox 2.

If you’ve followed me or my blog for any length of time, you know that advocating for Firefox in the enterprise has been something that I’ve been doing a very long time. Firefox 60 was released today with support for enterprise policies, including Windows Group Policy.