EnableTrackingProtection should have an option to whether set it to strict or standard about policy-templates HOT 6 OPEN

So this has come up before and it's probably time for me to just update the policy to allow you to set strict or standard.

from policy-templates.

I have a patch for this but it had some weird side effects. I'll try to get it landed soon.

from policy-templates.

Unfortunately the UI in preferences isn't tied to the policy, but you are "strict"

You can try setting:

browser.contentblocking.category

to "strict"

Using the Preferences policy.

from policy-templates.

I don't know if this will help you or not, @nyabinary, but I encountered this problem myself just the other day, and I couldn't satisfactorily solve it with the "Preferences" policy. At our organization, we want to set Enhanced Tracking Protection to "Strict" as the default value (not locked) with the user having the ability to change it. We also want to inherit as default any new changes to the meaning of "Strict" in the future (since that has historically changed over time), rather than explicitly custom-defining the individual settings that happen to map to "Strict" today but might not in the future.

I had to fall back to using AutoConfig instead of the policy engine to achieve what we were after, but I do believe the following works, though only for new profiles, not existing ones. Just as @mkaply said, the browser.contentblocking.category preference really only affects what the UI shows and not the underlying privacy settings, though I found that the exception to this is if the value is set on first run before any of the other values exist. In that particular case, then the individual privacy preferences do follow from the UI pref. I have these lines in our firefox.cfg:

// Instead of configuring every little micro-setting related to cookie & tracking protection,
// we just want to set Enhanced Tracking Protection to "Strict" and accept whatever the
// latest defaults for that macro-setting are from Mozilla, since it evolves over time.
// We don't want to lock the value, but setting a default value by "Preferences" policy
// doesn't work, since Firefox always treats this as a value set by the user with no default.
// The preference has a null value on first run, so we check for that and explicitly set
// our preferred default value as a user preference in that case.  The user can still
// override our value if they so choose.
if (!getPref("browser.contentblocking.category")) {
  pref("browser.contentblocking.category", "strict");
}

from policy-templates.

So this has come up before and it's probably time for me to just update the policy to allow you to set strict or standard.

That would be very nice :)

from policy-templates.

So this has come up before and it's probably time for me to just update the policy to allow you to set strict or standard.

Any update on this? (Would be nice, esp since their Social Tracking now too)
Also there is no option for blocking suspected fingerprinters in all websites (instead of just private windows) via policies yet right?

from policy-templates.