ESR128 - check protocol handling

might be others

• 1827827 add payto protocol to the registerProtocolHandler safelist
• 1871955 add lbry to the registerProtocolHandler allowlist

@pierov feel free to close if we are covered - i.e we block all then allowlist

added FF128-esr label

added Disk Leak label

Let's keep this open for now, we'll deal with this when reviewing prefs (we usually do additional blocks for defense in depth IIRC).

Bonus: https://bugzilla.mozilla.org/show_bug.cgi?id=1056860

removed Disk Leak label

added Proxy Bypass label

marked this issue as related to #42356 (closed)

added 14.0 stable label

added Roadmap::Future label

added Task label

added All Platforms label

I'll drop this here: i think mailto handlers were ok from a TB/MB perspective?

• FF121+ Allow setting the browser as the OS default mailto handler
  • pref("browser.mailto.dualPrompt", false);
  • pref("browser.mailto.dualPrompt.os", false);
  • pref("browser.mailto.prompt.os", true);

Adding it to mullvad-browser#178.

mentioned in issue mullvad-browser#178

marked this issue as related to #42751 (closed)

mentioned in issue #42751 (closed)

removed Roadmap::Future label

added Next label

Related to #42356 (closed)

assigned to @ma1

No changes in the protocol handlers "safe" list between esr115 and esr128:

$ schemes () { git show $1:dom/base/Navigator.cpp | grep -A100 'const kSafeSchemes' | grep -m1 -B100  '}' | grep '".*"'; }; diff <(schemes upstream/tor-browser-128.2.0esr-14.0-1) <(schemes upstream/tor-browser-115.15.0esr-13.5-1) && echo "NO CHANGE";
NO CHANGE

closed