Skip to content

Bug 41584: Move some configuration options to base-browser level

Merge Info

Related Issues

Backport Timeline

  • Immediate - patchsets for critical bug fixes or other major blocker (e.g. fixes for a 0-day exploit) OR patchsets with trivial changes which do not need testing (e.g. fixes for typos or fixes easily verified in a local developer build)
  • Next Minor Stable Release - patchset that needs to be verified in nightly before backport
  • Eventually - patchset that needs to be verified in alpha before backport
  • No Backport - patchset for the next major stable

Upstream Merging

This commit is directly to base-browser, because Tor Browser already has all these settings.

Please notice that I'm changing the name of one file (mobile/android/basebrowser.configure), and it's the only change we might do to Tor Browser.

Otherwise, we could ignore this MR for Tor Browser, and be very careful when rebasing 102.8.

Issue Tracking

  • Link resolved issues with appropriate Release Prep issue for changelog generation
    • I am not sure to which version I should link: we don't have Base Browser versions, so the effects on Tor Browser are going to be seen in 12.5a3, even though we still haven't released 12.5a2.

Change Description

I've realized some telemetry and similar options were disabled in the Tor Browser mozconfig commit, but we could move them to base-browser, instead, so that also Privacy Browser has them.

Merge request reports

Loading