user.js: sticky: unofficial: extension breakage due to prefs
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.
🔶 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.
🔶 Use this format if you can
**pref(s)**: `prefname`
**extension(s)**:
**breakage**:
**site/support issue**:
**comments**:
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Reactions: 4
- Comments: 40 (17 by maintainers)
pref(s):
privacy.resistFingerprinting = trueextension(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 flipprivacy.resistFingerprintingtofalse, set your shortcut (e.gAlt + Z), flip RFP back totrue. Now your zapper shortcut should work on pages loaded from now on.^^ edited by 👖
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! 🎩
@rusty-snake @khius Funny, I was literally just about to comment about the exact same issue with first party isolation and Raindrop.io! I’ll be sure to try that workaround when I get home!
For what it’s worth, I did email the dev about it a few days ago about the issue and he added it to the troubleshooting pages.
Since I had pointed out the
dom.w3c_pointer_events.enabled-truerequirement 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.enabledset tofalseFor whom may be concerned. Of course it’s always better to use an extension which doesn’t appear to contradict our privacy settings.