Richard Pospesel authored Jun 08, 2018 and Matthew Finkel committed Mar 24, 2021

Encrypting pages hosted on Onion Services with SSL/TLS is redundant
(in terms of hiding content) as all traffic within the Tor network is
already fully encrypted.  Therefore, serving HTTP pages from an Onion
Service is more or less fine.

Prior to this patch, Tor Browser would mostly treat pages delivered
via Onion Services as well as pages delivered in the ordinary fashion
over the internet in the same way.  This created some inconsistencies
in behaviour and misinformation presented to the user relating to the
security of pages delivered via Onion Services:

 - HTTP Onion Service pages did not have any 'lock' icon indicating
   the site was secure
 - HTTP Onion Service pages would be marked as unencrypted in the Page
   Info screen
 - Mixed-mode content restrictions did not apply to HTTP Onion Service
   pages embedding Non-Onion HTTP content

This patch fixes the above issues, and also adds several new 'Onion'
icons to the mix to indicate all of the various permutations of Onion
Services hosted HTTP or HTTPS pages with HTTP or HTTPS content.

Strings for Onion Service Page Info page are pulled from Torbutton's
localization strings.

Richard Pospesel authored Mar 04, 2019 and Matthew Finkel committed Mar 24, 2021

This patch adds a new 'securitylevel' component to Tor Browser intended
to replace the torbutton 'Security Slider'.

This component adds a new Security Level toolbar button which visually
indicates the current global security level via icon (as defined by the
extensions.torbutton.security_slider pref), a drop-down hanger with a
short description of the current security level, and a new section in
the about:preferences#privacy page where users can change their current
security level. In addition, the hanger and the preferences page will
show a visual warning when the user has modified prefs associated with
the security level and provide a one-click 'Restore Defaults' button to
get the user back on recommended settings.

Strings used by this patch are pulled from the torbutton extension, but
en-US defaults are provided if there is an error loading from the
extension. With this patch applied, the usual work-flow of "./mach build
&& ./mach run" work as expected, even if the torbutton extension is
disabled.

Kathleen Brade authored May 23, 2017 and Matthew Finkel committed Mar 24, 2021

Only ship the pdfjs extension.

Georg Koppen authored May 22, 2017 and Matthew Finkel committed Mar 24, 2021

In the past the ClearKey system had not been compiled when specifying
--disable-eme. But that changed and it is even bundled nowadays (see:
Mozilla's bug 1300654). We don't want to ship it right now as the use
case for it is not really visible while the code had security
vulnerabilities in the past.

Mike Perry authored May 05, 2017 and Matthew Finkel committed Mar 24, 2021

eBay and Amazon don't treat Tor users very well. Accounts often get locked and
payments reversed.

Also:
Bug 16322: Update DuckDuckGo search engine

We are replacing the clearnet URL with an onion service one (thanks to a
patch by a cypherpunk) and are removing the duplicated DDG search
engine. Duplicating DDG happend due to bug 1061736 where Mozilla
included DDG itself into Firefox. Interestingly, this caused breaking
the DDG search if JavaScript is disabled as the Mozilla engine, which
gets loaded earlier, does not use the html version of the search page.
Moreover, the Mozilla engine tracked where the users were searching from
by adding a respective parameter to the search query. We got rid of that
feature as well.

Also:
This fixes bug 20809: the DuckDuckGo team has changed its server-side
code in a way that lets users with JavaScript enabled use the default
landing page while those without JavaScript available get redirected
directly to the non-JS page. We adapt the search engine URLs
accordingly.

Also fixes bug 29798 by making sure we only specify the Google search
engine we actually ship an .xml file for.

Also regression tests.

Kathleen Brade authored Nov 25, 2015 and Matthew Finkel committed Mar 24, 2021

Add an about:tbupdate page that displays the first section from
TorBrowser/Docs/ChangeLog.txt and includes a link to the remote
post-update page (typically our blog entry for the release).

Always load about:tbupdate in a content process, but implement the
code that reads the file system (changelog) in the chrome process
for compatibility with future sandboxing efforts.

Also fix bug 29440. Now about:tbupdate is styled as a fairly simple
changelog page that is designed to be displayed via a link that is on
about:tor.

Kathleen Brade authored Jan 13, 2017 and Matthew Finkel committed Mar 24, 2021

The following files are never updated:
  TorBrowser/Data/Browser/profiles.ini
  TorBrowser/Data/Browser/profile.default/bookmarks.html
  TorBrowser/Data/Tor/torrc
Mac OS: Store update metadata under TorBrowser/UpdateInfo.
Removed the %OS_VERSION% component from the update URL (13047) and
  added support for minSupportedOSVersion, an attribute of the
  <update> element that may be used to trigger Firefox's
  "unsupported platform" behavior.
Hide the "What's new" links (set app.releaseNotesURL value to about:blank).
Windows: disable "runas" code path in updater (15201).
Windows: avoid writing to the registry (16236).
Also includes fixes for tickets 13047, 13301, 13356, 13594, 15406,
  16014, 16909, 24476, and 25909.

Also fix Bug 26049: reduce the delay before the update prompt is displayed.
Instead of Firefox's 2 days, we use 1 hour (after which time the update
doorhanger will be displayed).

Also fix bug 27221: purge the startup cache if the Tor Browser
version changed (even if the Firefox version and build ID did
not change), e.g., after a minor Tor Browser update.

Also fix 32616: Disable GetSecureOutputDirectoryPath() functionality.

Bug 26048: potentially confusing "restart to update" message

Within the update doorhanger, remove the misleading message that mentions
that windows will be restored after an update is applied, and replace the
"Restart and Restore" button label with an existing
"Restart to update Tor Browser" string.

Bug 28885: notify users that update is downloading

Add a "Downloading Tor Browser update" item which appears in the
hamburger (app) menu while the update service is downloading a MAR
file. Before this change, the browser did not indicate to the user
that an update was in progress, which is especially confusing in
Tor Browser because downloads often take some time. If the user
clicks on the new menu item, the about dialog is opened to allow
the user to see download progress.

As part of this fix, the update service was changed to always show
update-related messages in the hamburger menu, even if the update
was started in the foreground via the about dialog or via the
"Check for Tor Browser Update" toolbar menu item. This change is
consistent with the Tor Browser goal of making sure users are
informed about the update process.

Removed #28885 parts of this patch which have been uplifted to Firefox.

teor authored Mar 13, 2017 and Matthew Finkel committed Mar 24, 2021

When macOS opens a document or selects a default browser, it sometimes
uses the CFBundleSignature. Changing from the Firefox MOZB signature to
a different signature TORB allows macOS to distinguish between Firefox
and Tor Browser.

Mike Perry authored Sep 10, 2013 and Matthew Finkel committed Mar 24, 2021

See also Bugs #5194, #7187, #8115, #8219.

This patch does some basic renaming of Firefox to TorBrowser. The rest of the
branding is done by images and icons.

Also fix bug 27905.

Bug 25702: Update Tor Browser icon to follow design guidelines

- Updated all of the branding in /browser/branding/official with new 'stable'
icon series.
- Updated /extensions/onboarding/content/img/tor-watermark.png with new icon and
add the source svg in the same directory
- Copied /browser/branding/official over /browser/branding/nightly and the new
/browser/branding/alpha directories. Replaced content with 'nightly' and
'alpha' icon series.
Updated VisualElements_70.png and VisualElements_150.png with updated icons in
each branding directory (fixes #22654)
- Updated firefox.VisualElementsManfiest.xml with updated colors in each
branding directory
- Updated content/identity-icons-brand.svg with Tor Browser icon (fixes #28111)
- Added firefox.svg to each branding directory from which all the other icons
are derived (apart from document.icns and document.ico)
- Added default256.png and default512.png icons
- Updated aboutTBUpdate.css to point to branding-aware icon128.png and removed
original icon
- Use the Tor Browser icon within devtools/client/themes/images/.

Bug 30631: Blurry Tor Browser icon on macOS app switcher

It would seem the png2icns tool does not generate correct icns files and
so on macOS the larger icons were missing resulting in blurry icons in
the OS chrome. Regenerated the padded icons in a macOS VM using
iconutil.

Bug 28196: preparations for using torbutton tor-browser-brand.ftl

A small change to Fluent FileSource class is required so that we
can register a new source without its supported locales being
counted as available locales for the browser.

Bug 31803: Replaced about:debugging logo with flat version

Alex Catarineu authored Feb 19, 2020 and Matthew Finkel committed Mar 24, 2021

Because of the non-restartless nature of Torbutton, it required
a two-stage installation process. On mobile, it was a problem,
because it was not loading when the user opened the browser for
the first time.

Moving it to tor-browser and making it a system extension allows it
to load when the user opens the browser for first time.

Additionally, this patch also fixes Bug 27611.

Bug 26321: New Circuit and New Identity menu items

Bug 14392: Make about:tor behave like other initial pages.

Bug 25013: Add torbutton as a tor-browser submodule

Kathleen Brade authored Feb 26, 2019 and Matthew Finkel committed Mar 24, 2021

Build and package Tor Launcher as part of the browser (similar to
how pdfjs is handled).

If a Tor Launcher extension is present in the user's profile, it is
removed.

Mike Perry authored Sep 10, 2013 and Matthew Finkel committed Mar 24, 2021

This hack directly includes our preference changes in omni.ja.

Bug 18292: Staged updates fail on Windows

Temporarily disable staged updates on Windows.

Bug 18297: Use separate Noto JP,KR,SC,TC fonts

Bug 23404: Add Noto Sans Buginese to the macOS whitelist

Bug 23745: Set dom.indexedDB.enabled = true

Bug 13575: Disable randomised Firefox HTTP cache decay user tests.
(Fernando Fernandez Mancera <ffmancera@riseup.net>)

Bug 17252: Enable session identifiers with FPI

Session tickets and session identifiers were isolated
by OriginAttributes, so we can re-enable them by
allowing the default value (true) of
"security.ssl.disable_session_identifiers".

The pref "security.enable_tls_session_tickets" is obsolete
(removed in https://bugzilla.mozilla.org/917049)

Bug 14952: Enable http/2 and AltSvc

In Firefox, SPDY/HTTP2 now uses Origin Attributes for
isolation of connections, push streams, origin frames, etc.
That means we get first-party isolation provided
"privacy.firstparty.isolate" is true. So in this patch, we
stop overriding "network.http.spdy.enabled" and
"network.http.spdy.enabled.http2".

Alternate Services also use Origin Attributes for isolation.
So we stop overriding
"network.http.altsvc.enabled" and "network.http.altsvc.oe"
as well.

(All 4 of the abovementioned "network.http.*" prefs adopt
Firefox 60ESR's default value of true.)

However, we want to disable HTTP/2 push for now, so we
set "network.http.spdy.allow-push" to false.

"network.http.spdy.enabled.http2draft" was removed in Bug 1132357.
"network.http.sped.enabled.v2" was removed in Bug 912550.
"network.http.sped.enabled.v3" was removed in Bug 1097944.
"network.http.sped.enabled.v3-1" was removed in Bug 1248197.

Bug 26114: addons.mozilla.org is not special
* Don't expose navigator.mozAddonManager on any site
* Don't block NoScript from modifying addons.mozilla.org or other sites

Enable ReaderView mode again (#27281).

Bug 29916: Make sure enterprise policies are disabled

Bug 2874: Block Components.interfaces from content

Bug 26146: Spoof HTTP User-Agent header for desktop platforms

In Tor Browser 8.0, the OS was revealed in both the HTTP User-Agent
header and to JavaScript code via navigator.userAgent. To avoid
leaking the OS inside each HTTP request (which many web servers
log), always use the Windows 7 OS value in the desktop User-Agent
header. We continue to allow access to the actual OS via JavaScript,
since doing so improves compatibility with web applications such
as GitHub and Google Docs.

Bug 12885: Windows Jump Lists fail for Tor Browser

Jumplist entries are stored in a binary file in:
  %APPDATA%\\Microsoft\Windows\Recent\CustomDestinations\
and has a name in the form
  [a-f0-9]+.customDestinations-ms

The hex at the front is unique per app, and is ultimately derived from
something called the 'App User Model ID' (AUMID) via some unknown
hashing method. The AUMID is provided as a key when programmatically
creating, updating, and deleting a jumplist. The default behaviour in
firefox is for the installer to define an AUMID for an app, and save it
in the registry so that the jumplist data can be removed by the
uninstaller.

However, the Tor Browser does not set this (or any other) regkey during
installation, so this codepath fails and the app's AUMID is left
undefined. As a result the app's AUMID ends up being defined by
windows, but unknowable by Tor Browser. This unknown AUMID is used to
create and modify the jumplist, but the delete API requires that we
provide the app's AUMID explicitly. Since we don't know what the AUMID
is (since the expected regkey where it is normally stored does not
exist) jumplist deletion will fail and we will leave behind a mostly
empty customDestinations-ms file. The name of the file is derived from
the binary path, so an enterprising person could reverse engineer how
that hex name is calculated, and generate the name for Tor Browser's
default Desktop installation path to determine whether a person had
used Tor Browser in the past.

The 'taskbar.grouping.useprofile' option that is enabled by this patch
works around this AUMID problem by having firefox.exe create it's own
AUMID based on the profile path (rather than looking for a regkey). This
way, if a user goes in and enables and disables jumplist entries, the
backing store is properly deleted.

Unfortunately, all windows users currently have this file lurking in
the above mentioned directory and this patch will not remove it since it
was created with an unknown AUMID. However, another patch could be
written which goes to that directory and deletes any item containing the
'Tor Browser' string.  See bug 28996.

Bug 31396: Disable indexedDB WebExtension storage backend.

Bug 30845: Make sure default themes and other internal extensions are enabled

Bug 28896: Enable extensions in private browsing by default

Bug 31065: Explicitly allow proxying localhost

Bug 31598: Enable letterboxing

Disable Presentation API everywhere

Bug 21549 - Use Firefox's WASM default pref. It is disabled at safer
security levels.

Bug 32321: Disable Mozilla's MitM pings

Bug 19890: Disable installation of system addons

By setting the URL to "" we make sure that already installed system
addons get deleted as well.

Bug 22548: Firefox downgrades VP9 videos to VP8.

On systems where H.264 is not available or no HWA, VP9 is preferred. But in Tor
Browser 7.0 all youtube videos are degraded to VP8.

This behaviour can be turned off by setting media.benchmark.vp9.threshold to 0.
All clients will get better experience and lower traffic, beause TBB doesn't
use "Use hardware acceleration when available".

Bug 25741 - TBA: Add mobile-override of 000-tor-browser prefs

Bug 16441: Suppress "Reset Tor Browser" prompt.

Bug 29120: Use the in-memory media cache and increase its maximum size.

Bug 33697: use old search config based on list.json

Bug 33855: Ensure that site-specific browser mode is disabled.

Bug 30682: Disable Intermediate CA Preloading.

Bug 40061: Omit the Windows default browser agent from the build

Bug 40140: Videos stop working with Tor Browser 10.0 on Windows

Bug 40308: Disable network partitioning until we evaluate dFPI

Bug 40322: Consider disabling network.connectivity-service.enabled

Bug 40383: Disable dom.enable_event_timing

Mike Perry authored May 06, 2013 and Matthew Finkel committed Mar 24, 2021

Also:
Bug #9829.1: new .mozconfig file for the new cross-compiler and ESR24
Changes needed to build Mac in 64bit
Bug 10715: Enable Webgl for mingw-w64 again.
Disable ICU when cross-compiling; clean-up.
Bug 15773: Enable ICU on OS X
Bug 15990: Don't build the sandbox with mingw-w64
Bug 12761: Switch to ESR 38 for OS X
Updating .mozconfig-asan
Bug 12516: Compile hardenend Tor Browser with -fwrapv
Bug 18331: Switch to Mozilla's toolchain for building Tor Browser for OS X
Bug 17858: Cannot create incremental MARs for hardened builds.
Define HOST_CFLAGS, etc. to avoid compiling programs such as mbsdiff
(which is part of mar-tools and is not distributed to end-users) with
ASan.
Bug 13419: Add back ICU for Windows
Bug 21239: Use GTK2 for ESR52 Linux builds
Bug 23025: Add hardening flags for macOS
Bug 24478: Enable debug assertions and tests in our ASan builds
--enable-proxy-bypass-protection
Bug 27597: ASan build option in tor-browser-build is broken

Bug 27623 - Export MOZILLA_OFFICIAL during desktop builds

This fixes a problem where some preferences had the wrong default value.
Also see bug 27472 where we made a similar fix for Android.

Bug 30463: Explicitly disable MOZ_TELEMETRY_REPORTING

Bug 31450: Set proper BINDGEN_CFLAGS for ASan builds

Add an --enable-tor-browser-data-outside-app-dir configure option

Add --with-tor-browser-version configure option

Bug 21849: Don't allow SSL key logging.

Bug 31457: disable per-installation profiles

The dedicated profiles (per-installation) feature does not interact
well with our bundled profiles on Linux and Windows, and it also causes
multiple profiles to be created on macOS under TorBrowser-Data.

Bug 31935: Disable profile downgrade protection.

Since Tor Browser does not support more than one profile, disable
the prompt and associated code that offers to create one when a
version downgrade situation is detected.

Bug 32493: Disable MOZ_SERVICES_HEALTHREPORT

Bug 25741 - TBA: Disable features at compile-time

MOZ_NATIVE_DEVICES for casting and the media player
MOZ_TELEMETRY_REPORTING for telemetry
MOZ_DATA_REPORTING for all data reporting preferences (crashreport, telemetry, geo)

Bug 25741 - TBA: Add default configure options in dedicated file

Define MOZ_ANDROID_NETWORK_STATE and MOZ_ANDROID_LOCATION

Bug 29859: Disable HLS support for now

Add --disable-tor-launcher build option

Add --enable-tor-browser-update build option

Bug 33734: Set MOZ_NORMANDY to False

Bug 33851: Omit Parental Controls.

Bug 40061: Omit the Windows default browser agent from the build

Bug 40211: Lower required build-tools version to 29.0.2

Bug 40252: Add --enable-rust-simd to our tor-browser mozconfig files

Backed out changeset 695194f849b1 (bug 1695666)

Differential Revision: https://phabricator.services.mozilla.com/D107973

ast -> 9e7c8cb022e19ad8a9270fee6c235c318ec70186
be -> 34b0f313c6a3e2a7cc9e3d1d349b10e1e3ce4381
cak -> 147db1f71e7e65a884e678cc227e55410cac5a07
da -> a5bd41d60c1fefad4c78bd0ce8925518a6a6fe86
de -> 9897887ebb3da8b2eda4ba5f466b8ad602e3fabf
el -> bb3ee973b3a450bf1230fd28083afccbec55b9de
en-CA -> ce8532b8b691c630ac58e2c47750e769ae42356b
eo -> d83ff24301ecca406da3fd1de6c2bc0064ab2136
es-AR -> 2a99fd7d10f0cdd8db624f0777762c75d8b29f03
et -> 7365923469c4e01557906c3d677f2f83892b1ff1
he -> 09eb38186b2d0712f68d2ee45b2af6f4ac28fafa
hsb -> f7bf22570b9f0beaf21a8dd6a52398e972f53062
ia -> ab5f840366f6e78c2a12ca4249c4740a00074eab
it -> d89ebbadc70c0e7cb1418290d1b838b564e36640
kab -> d3db8428d2a62eecd8cd149584da693cb0c6ca80
lt -> 101dfe7e79be8b1cf65151629990b771f4cfe156
nb-NO -> 005aa0fdaac8f486e0599218483a65acdc9b46c6
nl -> 4bd106514c8209e84a57e4be909ae1323d667542
nn-NO -> 210b9a6a0df7d7749c23cdcb6ff4d075b1945011
oc -> f03c2e240e00dcdaeeb318b71058f82274687a58
pt-BR -> 57998e1b3488d3039dad12ff234b04032416badc
pt-PT -> bb097d6b2ac2f87461fb19caf0816e11fb06cee1
rm -> 8a25d75d22c9078f4321547ef7169e2f60c181b9
ru -> 1e59a99a8a69559598eadb9327af357741637b21
sk -> 723a278fc7f17612b4613122b67fcd42d86120ca
th -> f10e6dbf375d41cb30e598faee55745a4c841838
tr -> e6d7841382b4eeefea86b429a8be0b04603b5a59
zh-TW -> 71dd0f71fbca07d9043a6ab92b231228db8cf4fb

be -> 9606f8c42572d8e2cd09056a800a45df45f2c7ac
cy -> 4a4d375bd1f519e8166eeddf9eeb6cd47e21b8ca
de -> addbd3987aaf5257883bbcc1307fd7bc7907d579
dsb -> 2e61c8a381d9d1f0cd11f0f31602c1bd90d6d555
el -> ee6845910d47a48b93f67fc8c814d8c39f89c09a
en-CA -> af52cacd5b329c5453535e98c312bf3523af6cd1
eo -> 082607578a6229efe9d3e3e5c162e3cc25a0f75a
fa -> 4ef6c033734f60813e7bdd1bb77d9170d66adc45
hsb -> 1d8ca6dfabc0d6f670de8024fb19cd8d62331396
hu -> 36d264dafd5ebaf75c2ce65516e9710cfdb5699c
it -> 3900702bc4c6be5e69674e068441771fc59d3f49
ka -> 246fa435851ae07a28d55e83de8bc657235debad
kab -> 82add5e18a4d99a3de8679f095ed4a73b6b58f97
ko -> 2f7176a090edd7a8e104125e2c18069ae1a7d34e
nn-NO -> 606c2f754a9b8db2c92fd23c571d6fc7fb3b9ae9
oc -> 5666b8037a7ed6b618bcf72e6471f74435c1ff27
pl -> 89af6ee170b76bda332f6789c7ac18ee1830d1ff
rm -> 1b58611f90913c9aa035b371da55584f34ffe47a
sl -> 2f3de4ef28065096add556fbec7afffc5a1b28c6
sv-SE -> 7f41b3018c5b0801e1e49ee1ba8881aefda7c558
uk -> 3871b42bf3d2113974dc774717781920297d0bad
vi -> c86d3e9174808d2e3d9b6723cca5a709a8f604c7
zh-CN -> 67c45846b9675fb92cbe5115c5ad2437f1ed9855
zh-TW -> 8ca14c01d87a3b49b18ff54b2ff8b7a6719d2672

ast -> f9c1a6df7946095e2b95b2764a970f582f666b27
cak -> 80f9aea27a342d402cc50333bc9e7da283b07212
cs -> dba5e4f4147769999c6ffadb7ddf9ae1a221605c
cy -> 7195eb7ed4bdb68e757dff4e8df515aa2fcc9d0d
dsb -> 1f1c6d50e7c2cb1c8903d97e27a8b17e8def6cae
el -> 7d690d6e94bce51dc3e5aa2743f83da8801efcc4
en-CA -> 8c756691f37bc72a67ca6bf88f91bf5ae7b86a28
en-GB -> bda893a89524ba876b0fc4aa532dd7e4ebbebe9a
eo -> 0c98f3ad0e3a6ff7e8eccf8df22ced27af255098
es-AR -> beb33c6e6147452df4cbbfba7491c95ab54a8232
eu -> dc57059d857e45fa7c8501eb62416b30f7fe3c57
fi -> 731932a122991855f6c435ef27cb7cad13b11409
fr -> b4f22c3e3754839767993f899d9b830282e3ac04
fy-NL -> a88324d7e4d7d66e61a163616230bd7ddd430e45
gn -> 4af4c66903929e0015b980d24ecabefe377032ff
he -> 63b5fa913bdc44562de456347abb08ac6dce30ff
hr -> 9c7145ab297179b9b5ab3c7146107474816d49b7
hsb -> f503feeacd3de6017c566dd6e1fb664eef9e971a
hu -> f72b5fdbde6a415192490dd539df4958367f2e3d
ia -> f6b1fcfc279dcaca009cb3ab056ac7039a9aee5b
id -> f31ab32b7e4468d6333849347fdca7c5dfe099c9
it -> 5762764d9bdd29e8f348623caf6c2520f247c743
ja -> a2185d75cd2a294201a4cf765b3dd64048f11706
ja-JP-mac -> 5c0667ad2749db5195cb6d73d31e1814ffe47a63
kab -> 1e0405fbf683e4c77f53799a2cf5461420d08962
kk -> 596e3b849366608b6d02a8596d4f432f874f8749
km -> 3a3811ffc3e69bb6b8b4432896b72c3376d8c5ae
ko -> d08e0f99a4d220b5efc796ed3fb2ecb99140952f
lt -> bbb7016937ce1a6c40eb3a0d60ba3ec71b30baa1
nb-NO -> 45e3bbe332bc00ca0b13427a2e956dc863d305fe
nl -> 09b7920318cc214708bf7cedb15e3d35cd0e2b97
nn-NO -> 637fe1f40c8fac41b17c7957ba7a78d317fb1ef0
oc -> 7815ca25e7919890da9e246b2b03fc849228aa61
pt-BR -> 5449e55ac4481d808dbf9bcd82825d5d5f8e79ca
pt-PT -> c4e6c24807ad044d24201955f661aa31575fec7c
rm -> 30d8ed81e7d881e2d65738d5244269c13a0cefc2
sk -> 2fd5a67651725030e876225139f1f0fcaa8e1526
sl -> 623ee909b9e87baccd7e61e5d5a743005a0f5470
sr -> e15478b1caad2f356da3fad5e36aff1557c178f1
sv-SE -> 77e1df415d2fd4d56e50eedc73ebad99cdb6cd0d
th -> d2f3c8ae720630bf844066dca4570728e51c01de
tr -> 37765fc13ff060e3da1759c8e86d78652bac4f86
uk -> b8229f87f42246308c70461bb1c7dda52219e027
vi -> dec52af6d9ade86cf44a41f533c7d21ea9aeb43e
zh-CN -> dece9dd30077d64b147303b4f881063599bbd1df
zh-TW -> d0cae1e5f25cd0b06a9f81f874a801a269629134

Bug 1673742 - browser_save_video_frame.js should clear the mockTransferCallback before resolving the waitForTransferComplete promise, r=mconley. a=test-only

Differential Revision: https://phabricator.services.mozilla.com/D107853

tab.hasTabPermission indirectly triggers an access to
browser.currentURI, which for lazy tab browsers causes an incorrect
value to be cached. To avoid this, skip the call to hasTabPermission.

Differential Revision: https://phabricator.services.mozilla.com/D106622

Differential Revision: https://phabricator.services.mozilla.com/D106317

Differential Revision: https://phabricator.services.mozilla.com/D107525

Bug 1696187 - Enable URL top site -> search shortcut conversion for remote settings. r=mikedeboer, a=jcristau

Differential Revision: https://phabricator.services.mozilla.com/D107796

Bug 1697035 - Change quick suggest SUMO support page from "sponsored-search" to "firefox-suggest". r=daleharvey, a=jcristau

Differential Revision: https://phabricator.services.mozilla.com/D107541

Differential Revision: https://phabricator.services.mozilla.com/D107670

el -> fdba98d832286e5151877799adfd93a955d4a435
es-AR -> 4f75f1153715b457f2ac2fc946d4d82c4438e9f0
eu -> 5f8eafa52d7951bf605a15ac0926db21a4aa9eca
gn -> 686b8b10e14f154cc9103abc6e29d29e05e82d7c
he -> a82bb26bf1e83f13840dba148d0613c9b4f81354
hsb -> cee831802ce68a89a5ee8c81910ccb686ef57026
hu -> eb3f108e29d764bf061ea18ad4c44526395cf403
it -> 95a3720ff69aea98352d92fdb787b3669e1ae480
kk -> d9b234f3e3e332645c7df30e6b6c976ae4278b5f
ko -> 0d2563926299e002bb76d0acc3b5bdc87b2b97c3
nb-NO -> 2138670be10b1b47208f44e02ff16f78d1c7afd4
nl -> 2cafdfc496a0385e96959e4f368da2f97c0c11fd
nn-NO -> a690cab6b382af9cad6b3aee62b531fb3e32e0dd
oc -> 53013833eea63ecd559f3db2178398fbe3a9dea9
pt-BR -> d5f4fb76f0a40ad2783983c27bc615b1b4a8d0fe
sl -> b05c0140743e4baad3afc134b23b554307591b4f
uk -> 7b1a5b3e20e715958bf98af16c9b058017f3c674
zh-CN -> e575530b7ba7618a46d029413563d115d8a45339
zh-TW -> a52add7ae6751ad6c12bc096669fcbc85c761c43

be -> e19f2b756cef5aed09cd883a29a46392ed3f5a66
eo -> 0ecd5481c0105896f8ff6202d2710b970c9e964a
eu -> 09f1f47e57a53f7ddc17300826c59b2796a31584
fr -> 87f43fb0952d01d56af79798f6bca3518c934116
hi-IN -> 852a41e4b4bef70840a43fc4f5f485fff477df47
ia -> 8ba9c9ac5bf0a5c1eeca2ebda08e622fed1e3235
it -> af9f6d7799eaac7a644f8d7a590e1d6fad29b3ba
ja -> 67f7a4861e8487425aadd0928b151bebe65f0a8a
ja-JP-mac -> c1bb80c8b5c9a74ff5bd9287938c40f5bb60322b
kk -> b8c6a053585a118bab34c69fd5173fd514c6e449
nb-NO -> 0477e68001ab538ee8f777fe7f88b1c13481ab79
oc -> ccb69ccb1ce0b2c5408cbe4ff833d288ee8d4a3c
rm -> fd097840ed70051823bc1f54aefdf10c4f001736
th -> 057f22c124189046cfbf0024dfe7c5b4705c225c

Before decoupling the permission panel in Bug 1596897, the permission indicator was
not shown if we had a blocked permission icon to show instead. With the decoupled
permissions panel it needs to be shown whenever we have permissions listed in the
panel. The granted permissions icon is now the anchor for the panel.

Differential Revision: https://phabricator.services.mozilla.com/D106771

be -> f9a17c1712478b7362d16445c695046bae22a79a
br -> a87d196cd703011a8b9e8c482610be95d13b7fda
ca -> b44c810e601be4e0ca43238439f228beddda9c08
da -> d6299f0d25c30071604b6c2b7f1f176953bdc735
de -> 00cbd8bb573513dd37083f78dfc7d0e8a82d26f3
el -> 5d689b611f59bfda8c373903777585f92d27fb9f
eo -> 019dde10714866c154b79be2ca78b1dc46cd640d
es-AR -> 16f5f953c1c6301ca12a7505829a65776a9fcf2c
es-CL -> 218eccb5361e67113e679ae25a6695087a6808d5
es-ES -> d334276187b04e5c065ff73a48c4f7ffac5e0046
et -> 3c0854788de39632c02c92250511bc67e531cc0c
fr -> 08055371daa1f264e5301ac82411bee75b8181da
fy-NL -> 6dadbe0aad7102b9a9706c6924553d8ccfb7b11f
gn -> ba5a259209c4e646a3d76aedf77cf39da17d8a63
hi-IN -> 09b733ff9196623ff8410f4ab691a3af8d704023
hu -> 202f4b5a7910d0288479f336428546103b2664eb
ia -> 0b1ee6aba9f89fce965a10c0778baa9ad5561386
kk -> aa3907698fdf494b70dbe4f192023cf6606f2eab
lt -> e286569047c0a676fca3dd9c0e8cef77b0ee1c7a
oc -> 142a0c7c01386aa4f12219eccdce3b301d654365
pt-BR -> 6f6722e47a05cfa81d7b36dee86e8a14b013caae
pt-PT -> 3eb643528ac23db40a0a36b0e0a5de15f6e280ff
ru -> 3d2ae9a448be34741980b5ce9f0b8a7f6a888f58
sr -> 961ea26252a834402e919f723e1bcecf8113b112
vi -> 5097b99464f3036e5ef9eca94f35ca7d65efd44b

cak -> 5afd7b4e3f1dbe2ccf16fed6a52a09842f4ec294
da -> d78f07f6252934c54da4a6c1b033c92226ab858a
el -> 3510cc036ddc164cfcc264bb2f8f21c2b7d0f22b
eo -> 47302a6e30f61cddb2130f414ba167929ccfdec7
es-CL -> 583bd8fb5ff9cb2a0591d450eebba54bdf528f1f
fi -> d1101de366559133173ef6dd3e423de8da38c244
hr -> 80c7f5cf2aa83769d07611802f5674d4aaa39da4
ia -> 4d9fa130b239174984bb06fd9534cfcc5d416ed0
kk -> 6d6de91fb85364010a61bb609eb5bba4241596c8
lt -> c5e933134b81f6c0468bf84452650216590388b6
nn-NO -> d09674c4e093d2885c5d941a9ecce176ca5c81b9
ru -> 1ab6e2f8a253669a4b9634b4392d2828419c16bb
sl -> 97e8ccfd017cc6e889427bacbf509c026754a942
tr -> 072dbc27e99da177668e5543e829a51b26d6185c

cak -> f37fbac8ae72d3ecd819d6224a519b08ff41e4ca
de -> 5c2e50907f9b986e263c6c3ee3cdcc9d61b03b52
dsb -> 9c9c687d8792d2222f2a685e5aae2c7bd6d8cea7
et -> cbfbd5ef672171264b30b30fa8deb85a90a0d78c
fi -> 9586e6d5a4d441ac0c7df3446bb00ac147aaac47
hsb -> 26cf86464cae9f6bf8d0ea3ba8f97232014c87c9
hu -> 5de48f167b48583d44f7a09e16d771b2c0d7f6b2
ia -> d2b76a3b4034f36c9407e7aebe82e641dd45c98b
ka -> 2c4e76a22d27eecfb86f5132141f14ecab10b317
kab -> 79eec3c0f52b300536f4e77d61b5ac97138d650b
ko -> eefb1803c26e89273f4f0a3ce3079bc65d362ed8
lt -> a9c48e509c6ff2c5875e9d9d9436e34b0fcdf24d
pa-IN -> 290f751e36b955ff0820412c880d4995f3d36a5e
pl -> c245d5fbda679d67637156c20a319786df893f12
pt-BR -> 07f029f2869ba00381a54a402eed642e49b254d5
zh-CN -> 6922e62afaff560ef9ab50b9484b7fd6e5e66b81

cy -> 7c9ee1d240d733756ac1d57db603bb7ce1b31ac8
de -> fc79f430a1a2bbeaf5fc5e7c6007584eef4814d8
dsb -> c62b593074d828a01e14a10b7d5400f8161b684e
en-GB -> 11251d0bee34b3970506646dab241af73caaf3ff
es-AR -> 840ecc44aa14aa1f3c51e8307ecfdd9016fee53c
fa -> 9122ab2a8c096c8e5d4aeb9792e13fe77812e5dc
gn -> 54e05d70d159b502a983a22ef77a6e22f5a9c1d2
hsb -> 49797cdb8e1f9775bada8e2d85c3a098633aa5b0
ia -> f973e894eedb3c9f692632377c064cacd3a56165
it -> e80120436229ce8febc8ef5801bea5311a87d941
kab -> 42c13f4608f8c7a917d7abcdf36fc9da12c70e8c
kk -> 54b061ce346c3cdaa9df23a5c2b1a2f5a5e9cd2a
ko -> b312d7a036bd8b8716c4bb7ebd21369827bd2e18
nl -> 10ca045e001682fb7cf69c16beac98051209c893
oc -> 2e25e1e9273ec907071d3afee44d00ca35dc0617
rm -> 7f4d395a08e74859ff0fb947249dd7536f2a91a7
sv-SE -> 583d2dbb8fe04eafc5b4e927823736ecd07620ee
tr -> 50700d3abdf3d019c54cd93f1f0af7bd7648e6b0
uk -> f88cf7af88a9d1962f11f073c406486cbb3bfe38
zh-CN -> 59df069c5736df81677f3988278f754b178eafd3