Debugging faciliites.

This commits makes it possible to disable OS spoofing in the HTTP
User-Agent header, to see if matching header and JS property improve
usability.

Besides disabling the "Delete on close checkbox", disable also the
"Manage Exceptions" button when always using PBM.

about:preferences allow to override some of our defaults, that could
be fingeprintable or have some other unwanted consequences.

boklm authored 2 years ago and Pier Angelo Vendrame committed 1 year ago

MB 256: Add mullvad-browser nightly mar signing key

henry authored 1 year ago and Pier Angelo Vendrame committed 1 year ago

Bug 271: Do not open update override page in a new tab, and show in
about:mullvad-browser instead.

s/privacy-browser/mullvad-browser/

MB 71: Set the updater base URL to Mullvad domain

This commit disables the about:login page and removes the "Login and
Password" section of about:preferences.

We do not do anything to the real password manager of Firefox, that is
in toolkit: it contains C++ parts that make it difficult to actually
prevent it from being built..

Finally, we modify the the function that opens about:login to report an
error in the console so that we can quickly get a backtrace to the code
that tries to use it.

henry authored 1 year ago and Pier Angelo Vendrame committed 1 year ago

Bug 271: Show update in about:mullvad-browser

MB 270: Update support email

Also:
#57: Purge unneeded about: pages

We install a few addons from the distribution directory, but they are
not automatically enabled for PBM mode.
This commit modifies the code that installs them to also add the PBM
permission to the known ones.

Bug 42398: Include Alpha and Nightly in MOZ_APP_DISPLAYNAME.

See also:
#5: Product name and directory customization
#12: Create new branding directories and integrate Mullvad icons+branding
#14: Remove Default Built-in bookmarks
#35: Add custom PDF icons for Windows builds
#48: Replace Mozilla copyright and legal trademarks in mullvadbrowser.exe metadata
#51: Update trademark string
#104: Update shipped dll metadata copyright/licensing info
#107: Add alpha and nightly icons

MB 80: Enable the default browser agent

s/privacy-browser/mullvad-browser/

This commit implmenents the the Base Browser's version of _migrateUI.

ma1 authored 1 year ago and Pier Angelo Vendrame committed 1 year ago

Bug 42236: Let users decide whether to load their home page on new identity.

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.

Bug 40125: Expose Security Level pref in GeckoView

henry authored 1 year ago and Pier Angelo Vendrame committed 1 year ago

This hides it from both the toolbar and the unified extensions panel.

We also hide the unified-extension-button if the panel would be empty:
not including the NoScript button when it is hidden. As a result, this
will be hidden by default until a user installs another extension (or
shows the NoScript button and unpins it).

Matthew Finkel authored 3 years ago and Pier Angelo Vendrame committed 1 year ago

Bug 40253: Explicitly allow NoScript in Private Browsing mode.

Remove the items not compatible with our features (such as history) from
the migration wizard.

On Linux, allow to specify an alternative home directory, since we
usually change $HOME in our startup script.

Firefox strings use { -brand-product-name }.
As a result, it seems that the fork is recommending extensions, whereas
AMO curators are doing that.
So, we replace the strings with custom ones that clarify that Mozilla is
recommending them.

We assign the strings with JS because our translation backend does not
support Fluent attributes, yet, but once it does, we should switch to
them, instead.

Upstream bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1825033