etesync
Privacy Badger Firefox extension blocks login
Firefox 85
Privacy Badger is causing the login page to hang forever once user has entered creds and clicked LOG IN.
Console error message indicates a CSP issue
See screenshot attached
On this system, CPU load is increasing from 30% to 50% when clicking Log In, and going back to 30% when I close the window.
Edit: it might just be the "KnightRider bar" in the Loading window causing the CPU increase. This is an old laptop...
The CSP should only block the offline service worker for the Progressive Web App functionality, not the login. I do manage to login even with these errors in the console, and with Privacy Badger, but I'm using my own server.
What makes you say that it's an incompatibility with Privacy Badger?
Edit: I see that utils.js is a Privacy Badger file, but my understanding is that the CSP actually prevents the extensions from injecting a script so I'd guess it actually prevents them from working.
It seems like it's a known bug in Firefox: https://bugzilla.mozilla.org/show_bug.cgi?id=1446231
Do you know where the content-script.js comes from ? I don't have it, but I have other errors with other extensions.
I think I just witnessed this issue…
The problem seems to happen only in Firefox (tested on Chromium also), even without any add-on. I wonder if it's an issue with CPU load: it only happens when I have several apps and the Dev Tools open, and not consistently.
The issue happens during the call to Etebase.Account.Login().
The argon2 web worker is spawned and then disappears from the Dev Tools debugger, but no error is reported.
Ah yes, I should have specified. It was indeed on FF and I had dev tools open as I was trying to diagnose #138
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ On Tuesday, February 2nd, 2021 at 10:41, Kévin Commaille [email protected] wrote:
I think I just witnessed this issue…
The problem seems to happen only in Firefox (tested on Chromium also), even without any add-on. I wonder if it's an issue with CPU load: it only happens when I have several apps and the Dev Tools open, and not consistently.
The issue happens during the call to Etebase.Account.Login(). The argon2 web worker is spawned and then disappears from the Dev Tools debugger, but no error is reported.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.