We can use these to cover important information for the time-being, until the website is ready - once it is, we'll move content from here to there
Signed-off-by: celenity <celenity@celenity.dev>
This also sets the browser theme back to the default of automatic/following the device's theme, since the website appearance is what's actually fingerprintable
Signed-off-by: celenity <celenity@celenity.dev>
This is probably the last aggressive setting that we inherited from Mull, known to cause a significant amount of breakage on sites - now that we have UI toggles for it, we can set it back to the saner default (This is also the default for ex. LibreWolf, Tor Browser, etc)
So we've now officially eliminated nearly all notable breakage out of the box, which I think is great - I feel like we've been working towards this for a while now :)
Signed-off-by: celenity <celenity@celenity.dev>
Notably, this removes the SFW providers - unnecessary, not really effective anyways (if the goal is parental controls... the setting can be easily changed from `about:preferences#privacy`, so I don't think it makes sense for that purpose either - and in general, I don't really think we should be promoting censorship
This also re-organizes the providers to be alphabetical, simplifies the names, adds flags to indiciate the jurisdictions, etc.
Signed-off-by: celenity <celenity@celenity.dev>
Annoying and unwanted (especially now that we support wallpapers...). This same menu can still be accessed by selecting the 3 dots -> `Customize homepage`, or by navigating to `Settings` -> `General` -> `Homepage`.
Signed-off-by: celenity <celenity@celenity.dev>
The initial set of wallpapers are taken from Fennec F-Droid (Available under the Unsplash License): https://gitlab.com/relan/fennecmedia, but we'll be able to expand this and add additional wallpapers in the future
Signed-off-by: celenity <celenity@celenity.dev>
I did some extensive testing and research, this should help to remove further reduce the complexity of our patches
Signed-off-by: celenity <celenity@celenity.dev>
This does NOT impact the initial install of uBlock Origin, and it doesn't impact add-ons installed from local files - it controls installs from websites
We limit the websites allowed to install add-ons to a select few anyways, but we should discourage users from installing add-ons in general unless necessary, due to the privacy and security concerns
So this improves security for users overall, while still providing them with the freedom to re-enable installation of add-ons if desired, right from the UI
Signed-off-by: celenity <celenity@celenity.dev>
Currently, to play DRM-controlled content, users are enabling EME and Widevine from the `about:config` by setting `media.eme.enabled` and `media.mediadrm-widevinecdm.visible` to `true`. This *technically* works, but the problem is that we remove the EME permission UI in `fenix-liberate.patch` - so if a user enables EME with the `media.eme.enabled` pref (which we know users are), it allows *all* websites to use DRM, without prompting.
So for folks who insist on enabling/using DRM (which I will emphasize is NOT supported or recommended), this adds a way for them to enable it at their discretion, while still being able to control which sites can and can't use it, like vanilla Firefox allows.
This adds two hidden/secret settings that function as follows:
- `Enable Encrypted Media Extensions (EME)` - When enabled, this sets `media.eme.enabled` to true, and it exposes the UI for controlling the DRM site permission.
- `Enable Widevine CDM` - This depends on the `Enable Encrypted Media Extensions (EME)` setting. When enabled, it sets `media.mediadrm-widevinecdm.visible` to `true`.
Signed-off-by: celenity <celenity@celenity.dev>
For reference, Mozilla uses this for their Safe Browsing toggle in Firefox Focus - doesn't make sense not to leverage the work they've already done. If/when they add a Safe Browsing toggle to Fenix upstream, this is also likely the same approach they'll use.
Signed-off-by: celenity <celenity@celenity.dev>
