Remove the status bar panel (the status bar was removed in Firefox 4).
Remove unused Firefox version check variables.

Remove some unused functions and commented out code.

Remove toggle support from torbutton_set_timezone().

Rename torbutton_close_on_toggle() to torbutton_close_tabs_on_new_identity()
and remove toggle support.

Remove a lot of toggle logic, including extensions.torbutton.tor_enabled
and related preferences.

Remove the dual cookie jar support since Tor can no longer be turned off.

Change the behavior of the "Restore Defaults" button in the Privacy
and Security Settings window to no longer reset the browser's proxy
preferences. Our general philosophy is that if Torbutton does not
provide a GUI for changing a preference, Torbutton should not modify
the preference. The exceptions are that Torbutton still supports the
TOR_SOCKS_PORT and TOR_TRANSPROXY environment variables.

Remove the outdated "Disable Torbutton to change these settings"
message from the Firefox proxy settings dialog.

Remove torbutton_check_socks_remote_dns() since SOCKS remote DNS is
supported by all modern versions of Firefox.

Remove torbutton_has_good_socks() since it was testing for Firefox 5
or newer.

Remove the remains of the Torbutton settings panel (which was hidden by
the fix for bug 14630).

CHANGELOG update, version bump

Remove remaining things needed for fixing #9901.

Kathleen Brade authored Jun 29, 2016 and Georg Koppen committed Jul 17, 2016

Display the external app confirmation dialog in response to the new
"external-app-requested" observer service notification. Remove
messy overrides of Mozilla components and console log filtering.

Remove obsolete "on-modify-drag-list" observer and pre-Firefox 4.0
module registration code from the External App Handler component.

We are exempting `javascript.options.asmjs` from the Security Slider for
now and set it to `false` by default (which is done by a separate
Tor Browser patch).

This is a stopgap until at least the linkability concerns in #19417 are
addressed.

Kathleen Brade authored Jul 15, 2016 and Georg Koppen committed Jul 17, 2016

When displaying the "Are you sure you want to enable plugins?" prompt,
always use the top-most browser window as the parent window. This avoids
problems caused by using the Privacy and Security Settings dialog, which
is closing, as the parent.

The browser's behavior is different depending on if a given internal
resource is available or not, regardless of the fact that the actual
body will not load due to the various safeguards and checks.

This normalizes the behavior by denying all redirects destined for URLs
with proscribed browser internal schemes (`resource`, `about`, `chrome`).

This patch clears the asmjscache (and the IndexedDB storage) on
New Identity and during start-up. The latter is a suboptimal workaround
we deploy until the asmjscache is Private Browsing Mode aware.
InedxedDB storage is not so urgent as IndexedDB is not working in
Private Browsing Mode anyway.

Most addons do not set `contentaccessible=yes`, however behavior should
be consistent even if such addons are installed.

This does not affect any of the standard addons shipped with Tor Browser, but
will break user installed addons that depend on actually being able to
access `chrome://` URLs in this manner.

Based on ResourceFilter: A direct workaround for https://bugzil.la/863246
https://notabug.org/desktopd/no-resource-uri-leak/src/master/src/resource-filter/content-policy.js

Yawning Angel authored Jun 07, 2016 and Georg Koppen committed Jun 10, 2016

Additionally clear out the domain isolator state on `New Identity`.  In
theory this removes the need to explicitly issue a `NEWNYM` as new
circuits will be used for all subsequent requests, including those made
via the catch-all circuit.

Yawning Angel authored Jun 07, 2016 and Georg Koppen committed Jun 10, 2016

When creating a domain isolation nonce, 128 bits of entropy is drawn
from a cryptographic source and saved on a per-domain basis.  The new
circuit behavior is changed to regenerate the nonce, instead of
incrementing a counter.

This allows the "right thing" to happen when the same tor instance is
used across multiple Tor Browser sessions, for example when using a
system wide tor, or a magic anonymity box.

CHANGELOG update, version bump

Remove default preferences that are not used.

Remove unused property strings.

Remove unused entities.
Remove unused "about.xul" and associated entities.

Thanks to cpwc for the patch.

Version bumps, changelog update

Our usage of |let| does not work anymore since changes in Firefox 44
landed. See: https://bugzilla.mozilla.org/show_bug.cgi?id=589199.

Kathleen Brade authored Mar 04, 2016 and Georg Koppen committed Mar 19, 2016

Add profileMigrationFailed string that is used by Tor Browser.

We follow Mozilla's handling of the graphite library and apply it to
all security slider levels.

CHANGELOG update, translation update, version bump

Mike Perry authored Feb 18, 2016 and Georg Koppen committed Mar 04, 2016

Creates a hidden torbutton pref, which if set, allows Tor Browser to work with
non-Tor proxies (by disabling our use of SOCKS u+p auth).

Enabling this pref also enables NoScript ABE (to prevent proxied connections
from hitting localhost/RFC1918) and executes New Identity.

Arthur Edelstein authored Feb 05, 2016 and Georg Koppen committed Feb 19, 2016

Also, when logging, don't show a bunch of extra newlines.

See https://trac.torproject.org/16990#comment:28

For the about:tor content window, use
nsIDOMWindowUtils.screenPixelsPerCSSPixel instead of
window.devicePixelRatio to compensate for a retina display and for
content zoom (devicePixelRatio always returns 1.0 for content windows
due to the fix for bug 13875).