Proton Pass breaks prowlarr on firefox since today
Prowlarr returns There was an error loading this page when I click on an app and other sites. When I disable proton pass, it works as usual. Any idea how to solve it?
Permission denied to access property "matches"
at toArray( (webpack://prowlarr/node_modules/focus-lock/dist/es2015/utils/tabUtils.js:8:26)
at toArray( (webpack://prowlarr/node_modules/focus-lock/dist/es2015/utils/tabUtils.js:7:59)
at parents.reduce(function (webpack://prowlarr/node_modules/focus-lock/dist/es2015/utils/tabUtils.js:22:64)
at parents.reduce(function (webpack://prowlarr/node_modules/focus-lock/dist/es2015/utils/tabUtils.js:20:19)
at getAllTabbableNodes (webpack://prowlarr/node_modules/focus-lock/dist/es2015/utils/DOMutils.js:31:43)
at getAllTabbableNodes (webpack://prowlarr/node_modules/focus-lock/dist/es2015/focusMerge.js:37:41)
at setFocus (webpack://prowlarr/node_modules/focus-lock/dist/es2015/setFocus.js:21:34)
at withinHost (webpack://prowlarr/node_modules/react-focus-lock/dist/es2015/Trap.js:125:23)
at lastTrap.returnFocus (webpack://prowlarr/node_modules/react-focus-lock/dist/es2015/Trap.js:260:4)
at reducePropsToState(mountedInstances.map(function (webpack://prowlarr/node_modules/react-clientside-effect/lib/index.es.js:34:6)
at componentDidUpdate (webpack://prowlarr/node_modules/react-clientside-effect/lib/index.es.js:57:8)
at Yi (webpack://prowlarr/node_modules/react-dom/cjs/react-dom.production.min.js:219:501)
at try{for (webpack://prowlarr/node_modules/react-dom/cjs/react-dom.production.min.js:259:159)
at unstable_next (webpack://prowlarr/node_modules/scheduler/cjs/scheduler.production.min.js:18:342)
at eg (webpack://prowlarr/node_modules/react-dom/cjs/react-dom.production.min.js:122:324)
at Uj (webpack://prowlarr/node_modules/react-dom/cjs/react-dom.production.min.js:252:281)
at Lj (webpack://prowlarr/node_modules/react-dom/cjs/react-dom.production.min.js:243:370)
at jg (webpack://prowlarr/node_modules/react-dom/cjs/react-dom.production.min.js:123:114)
at unstable_next (webpack://prowlarr/node_modules/scheduler/cjs/scheduler.production.min.js:18:342)
at eg (webpack://prowlarr/node_modules/react-dom/cjs/react-dom.production.min.js:122:324)
at jg (webpack://prowlarr/node_modules/react-dom/cjs/react-dom.production.min.js:123:63)
at eg (webpack://prowlarr/node_modules/react-dom/cjs/react-dom.production.min.js:122:427)
at Hb (webpack://prowlarr/node_modules/react-dom/cjs/react-dom.production.min.js:292:100)
at $c (webpack://prowlarr/node_modules/react-dom/cjs/react-dom.production.min.js:73:354)
Proton Pass is a password manager? I'm failing to see why it has anything to do with a web service that you're running. You should be asking in support for Proton Pass.
The error posted in the app is from the website itself. It's likely that the password manager is injecting something into the page which is causing errors.
There are many ways for this to go wrong, it has nothing to do with the web service itself.
Its breaking a shitload og stuff on Firefox right now...I can't reliably use my home assistant interface with it enabled, onshape won't load CAD models and I can't use drop-down menus on a lot of sites.
I don't know what the hell they did, but it's breaking everything.
Does bitwarden allow me to automatically create a new randomized email address for every new saved login I create, that forwards to my secret main address? That's the main thing that's keeping me with Proton. Every online account is a different email. When I start getting spam because one leaked, I simply delete that email address, problem solved. Something like the Gmail plus thing doesn't work since I can't arbitrarily delete an alias that way when I want to.
I reported the bug to Proton support and they said they are investigating but suggested I uninstall and reinstall the extension. I did and lo, my forms started working again. I can recommend you try to uninstall and reinstall too (disabling it was not enough).
Why would a random browser extension take it upon itself to snoop on your traffic to ensure that the websites you're using can't be used for illegal things, and then intentionally break it if it detects something it thinks it's illegitimate? That's a huge breach of privacy. It's just malware at that point. It's not like a court of law would hold your browser extensions responsible for your piracy. That's like blaming a cup holder because the car was used in a robbery.
No, I think this is just a bug. Especially since people have reported that the extension breaks other websites too.