User.js: sticky: unofficial: extension breakage due to prefs

[Thorin-Oakenpants]

The information in here is user submitted and not verified by this repo (unless stated). I will also not maintain or update or clean up this thread. Have at it, it's ALL yours - just look at the readme first.

:large_orange_diamond: read me

I am not against information being shared if it helps end users, but I am not interested in maintaining any lists of extension issues to do with prefs or adding info to the user.js (except those extensions we recommend)

• This user.js does not have a monopoly on pref changes. Extension breakage information belongs with the developer/support site.
  
  
  
  • Sometimes they can code fixes / fallbacks / workarounds
  
  
  • Sometimes they can detect the issue and alert the user
  
  
  • At the very least they can add something to the help section
  
  
• It just isn't feasible (time constraints, sheer numbers, constant code changes)
• The user.js is already lengthy & bulky

Do not ask for troubleshooting in here (open a new issue if you really need help). Keep this thread clean and tidy, we only need confirmation that pref(s) X caused extension(s) Y to break in Z manner. Link back to any developer discussions if need be.

:large_orange_diamond: Use this format if you can

**pref(s)**: `prefname`
**extension(s)**: 
**breakage**: 
**site/support issue**: 
**comments**: 

[Thorin-Oakenpants]

Thanks @mazesy
pref(s): dom.w3c_pointer_events.enabled-false
extension(s): Gesturefy in FF59+ and maybe other gesture type extensions
breakage: see support issue linked below
site/support issue: https://github.com/Robbendebiene/Gesturefy/issues/271
comments: RFP may take care of this one day: see 1363508

[Thorin-Oakenpants]

pref(s): dom.allow_cut_copy=false
extension(s): Copy on Select and other auto-copying extensions
breakage: doh!
site/support issue: N/A

[Thorin-Oakenpants]

pref(s): privacy.resistFingerprinting=true
extension(s): anything that uses canvas or depends on local time
breakage:

• canvas is blocked: 1412961 resolved fixed in FF61+ but 1453916 : still some issues
  
  
  
  • > until then, you can open about:debugging>Add-ons, click the extension's manifest.url and on that page, right click >View Page Info>Permissions and set a canvas exception
  
  
• extensions also get UTC 0 spoofed time zone

site/support issue: N/A
comments: known and will be dealt with in time (pun intended)

• 1377744 time zone spoof + extensions
• 1450398 RFP + extensions

[ghost]

Since I had pointed out thedom.w3c_pointer_events.enabled-true requirement for the _Gesturefy_ extension,
because the scenario of an extension requiring a pref to be set differently than what privacy suggests is not the ultimate,
maybe is is worth mentioning that another extension named _Foxy Gestures_, very similar (I'd even say better) to _Gesturefy_ exists that runs flawlessly withdom.w3c_pointer_events.enabled set to false

For whom may be concerned. Of course it's always better to use an extension which doesn't appear to contradict our privacy settings.

[Thorin-Oakenpants]

pref(s): security.OCSP.enabled=1 (this is FF's default value)
extension(s): Hoxx VPN Proxy and probably others
breakage: failure to use/log-in to VPN
site/support issue: #295
comments: security.OCSP.require may also be a factor in these sorts of cases. In the user.js we enforce a value of true, the default is false

[Thorin-Oakenpants]

Thanks @Pilford
pref(s): layout.css.font-loading-api.enabled=false
extension1: Save Page WE and probably other "save as" extensions
breakage: save silently fails, console warning: document.fonts is undefined
extension2: Reddit Enhancement Suite's options is completely blank
site/support issue: #592
comments: read the issue

Update June 2019: the pref was removed from the user.js

[Pilford]

From the developer of Save Page WE:

Save Page WE uses the CSS Font Loading Module to check which fonts are currently being used in the page that is being saved.

Without doing this check, Save Page WE would have to save all of the font files that are referenced in any CSS ‘@font-face’ rules. This would often make saved files much larger.

When saving the page, Save Page WE downloads the font files for the fonts that are currently being used in the page and (optionally) for WOFF fonts.

[aesthicc]

pref(s): network.auth.subresource-http-auth-allow = 1
extension(s): Torrent Control
breakage: failed login
site/support issue: https://github.com/Mika-/torrent-control

[powerman]

pref(s): dom.w3c_pointer_events.enabled-false
extension(s): Gesturefy in FF59+ and maybe other gesture type extensions
breakage: see support issue linked below
site/support issue: Robbendebiene/Gesturefy#271
comments: RFP may take care of this one day: see 1363508

This comment should be updated:

• RFP must be disabled for Gesturefy-2.x
• Gesturefy-1.2.2 should work with RPF
• 1363508 was resolved 5 months ago, but in FF 66.0 Gesturefy still doesn't work with RPF, so I suppose this bug didn't fixed this issue

[GitCurious]

pref(s): // user_pref("javascript.options.ion", false);
// user_pref("javascript.options.baselinejit", false);
extension(s): Ublock Origin
breakage: Significant delays opening pages when these are enabled
site/support issue: all
comments: I DO realise these are OFF by default but discovered by trial and error that these were responsible for the delays on Firefox since approx v.66.xx

[GIPeon]

pref(s): privacy.resistFingerprinting = true
extension(s): uBlock Origin (and probably any extensions using the Alt key in their options)
breakage: can't set shortcut keys in dashboard>settings (Alt+letter)
site/support issue: n/a
solution: Just flip privacy.resistFingerprinting to false, set your shortcut (e.g Alt + Z), flip RFP back to true. Now your zapper shortcut should work on pages loaded from now on.

^^ edited by :jeans:

Btw your troubleshooting tips and the script turned out to be very useful. I scratched my head quite some time trying to debug this, looking at possible console errors and stuff but nothing really pointed me in the RFP direction (or maybe my lack of experience, quite deep unfortunately, didn't allow me to find any correlation).

I take the chance to thank you all for all your commitment in this incredible work, very well done sirs! :tophat:

[Thorin-Oakenpants]

FYI

1576254: FF71+ (and supposed to get backported to the ESR)
pref(s): javascript.options.wasm
breakage: pref no longer applies to extensions

1564208: FF70+ and ESR68.1.0+
pref(s): svg.disabled
breakage: pref no longer applies to extensions

[sshockley]

Having dom.storage.next_gen=true appears to break the Kee add-on. With it enabled, this shows in the debug panel for Kee:

Content Security Policy: Couldn’t parse invalid host 'wasm-eval'
UnknownError: The operation failed for reasons unrelated to the database itself and not covered by any other error code. ExtensionStorageIDB.jsm:831
    normalizeStorageError resource://gre/modules/ExtensionStorageIDB.jsm:831
    method chrome://extensions/content/child/ext-storage.js:273
    AsyncFunctionThrow self-hosted:678
Failed to persist storage for principal: moz-extension://a89a86d1-eb13-4bb1-a064-6a5651978d2d ExtensionStorageIDB.jsm:758
    callback resource://gre/modules/ExtensionStorageIDB.jsm:758

The add-on shows the red "OFF" splat and is greyed out. Setting dom.storage.next_gen=false fixes it.

This started with FF83, but I'm not sure if that's coincidence.

[Thorin-Oakenpants]

This started with FF83, but I'm not sure if that's coincidence

I only added it to the user.js in the 11 days ago, so not a coincidence

Have you spoken to the extension developer? What happens if you try the extension in a new profile and add some data? When I get time I'll see what I can test, but some legwork from the dev would be helpful