This is a meta-issue tracking a bundle of issues, and as such is not in itself a Freedom issue (that it identified for each unblundled issue). Lowering priority accordingly.

This issue is considered solved in PureOS.
It is true that the solution used for PureOS is not ideal, but it is effective: Users cannot accidentally or sloppily make use of the EME implementation included with Firefox ESR as shipped with PureOS, because it requires manually editing plaintext files to enable that functionality.

@adfeno I notice you mention lack of help examining, and also that you rely on licensecheck for your examination.

Please note that it looks like adding /etc/firefox-esr/pureos.js is only masking the problem. The underlying implementation would still be built in the package and available in the source code. This has already been mentioned in the last paragraph of this comment: https://tracker.pureos.net/T902#16752

I reported this issue on my own (not driven by reports of others but from my prior knowledge in maintaining PureBrowser and therefore pretty exactly knowing how they differ).

The plan that was devised consists of two steps;

@jonas.smedegaard Did a user report this? Or is this bug from your own sleuthing? :-) I ask because sometimes the FSF rewards users who report freedom issues with GNU Bucks and there may be some at stake for reporting.

This is important as we do not want to implement any browser prompt to install an EME plugin.

@EchedeyLR https://packages.debian.org/source/testing/chromium

In T57#14719, @jonas.smedegaard wrote:

@mak Please stop block chromium - it does not contain non-free code and is no longer unclear about licensing.

Also see https://directory.fsf.org/wiki/Review:Chromium-REV-ID-1 or https://directory.fsf.org/wiki/Talk:Chromium (the first link might be moved to the last one). Iridium Browser suffers from the same issues (this is described in the references). Also as described there, none of the lists is exhaustive, as we/volunteers from FSD lack some contributors specific for this issue.

@EchedeyLR Thanks for investigating. Please however report any concrete findings as separate issues.

I think there is still a similar problem with Chromium like https://tracker.pureos.net/T663 due to Google dependence/promotion.

In T57#14719, @jonas.smedegaard wrote:

@mak Please stop block chromium - it does not contain non-free code and is no longer unclear about licensing.

If I remember, Chromium is not packaged on Trisquel due to more problems but I am not sure.

@mak Please stop block chromium - it does not contain non-free code and is no longer unclear about licensing.

Correction: This _is_ a freedom issue, not because it (optionally) uses nonfree (or rather closed-protocol) service but because (optionall, when configuring to use that protocol) it downloads nonfree software.

@sean.obrien I now clarified scopes of issues T110 and T156, and here.

This issue is now about PureBrowser linking to DuckDuckGo non-free JavaScript.

Even if this was meant (also) as a duplicate of T110, we can reuse it to track (only) the related issue of avoiding Javascript not Free licensed.

@zlatan.todoric LibreOffice build-depends on chromium, so this will be quite annoying.
Package is removed from PureOS now, but we will need to find a solution for LO...

@mak remove and block from re-entering the chromium package from archive as GNU-libre ML is pointing this out.

Fixed kodi finally arrived in PureOS.