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>
Unlike the previous patch, this doesn't break the installation of add-ons locally with the `Install extension from file` option (https://gitlab.com/ironfox-oss/IronFox/-/issues/112)
This now also allows users to specify websites they'd like to allow to install extensions with the `xpinstall.whitelist.add` pref, providing users with more freedom and control. The default list allows AMO (`addons.mozilla.org`), as well as AdGuard and Mullvad, to allow users to install those extensions directly from the devs (and for Mullvad's case, at all). In general we'll want to keep this list to a minimum, and users are NOT recommended to add domains here. In the future though, we can probably look into allowing installation from other specific trustworthy sources - fixes https://gitlab.com/ironfox-oss/IronFox/-/issues/102)
Signed-off-by: celenity <celenity@celenity.dev>
Unlike the previous patch, this doesn't break the installation of add-ons locally with the `Install extension from file` option (https://gitlab.com/ironfox-oss/IronFox/-/issues/112)
This now also allows users to specify websites they'd like to allow to install extensions with the `xpinstall.whitelist.add` pref, providing users with more freedom and control. The default list allows AMO (`addons.mozilla.org`), as well as AdGuard and Mullvad, to allow users to install those extensions directly from the devs (and for Mullvad's case, at all). In general we'll want to keep this list to a minimum, and users are NOT recommended to add domains here. In the future though, we can probably look into allowing installation from other specific trustworthy sources - fixes https://gitlab.com/ironfox-oss/IronFox/-/issues/102)
Signed-off-by: celenity <celenity@celenity.dev>
Unlike the previous patch, this doesn't break the installation of add-ons locally with the `Install extension from file` option (https://gitlab.com/ironfox-oss/IronFox/-/issues/112)
This now also allows users to specify websites they'd like to allow to install extensions with the `xpinstall.whitelist.add` pref, providing users with more freedom and control. The default list allows AMO (`addons.mozilla.org`), as well as AdGuard and Mullvad, to allow users to install those extensions directly from the devs (and for Mullvad's case, at all). In general we'll want to keep this list to a minimum, and users are NOT recommended to add domains here. In the future though, we can probably look into allowing installation from other specific trustworthy sources - fixes https://gitlab.com/ironfox-oss/IronFox/-/issues/102)
Signed-off-by: celenity <celenity@celenity.dev>
