[BUG] Proton Pass not working as expected #133

New issue

Closed

opened 2025-06-01 17:36:00 +02:00 by AnonSky · 2 comments

AnonSky commented

2025-06-01 17:36:00 +02:00

What version of Phoenix are you using?

2025.05.11.1

What version of Firefox are you using with Phoenix?

139.0.1

What operating system are you experiencing this issue on?

Other

Windows 11

Please explain the issue you are experiencing.

When using Proton Pass, the password generator feature does not work. It does not show the password and doesn't copy it into the clipboard.

### What version of Phoenix are you using? 2025.05.11.1 ### What version of Firefox are you using with Phoenix? 139.0.1 ### What operating system are you experiencing this issue on? Other ### Other Windows 11 ### Please explain the issue you are experiencing. When using Proton Pass, the password generator feature does not work. It does not show the password and doesn't copy it into the clipboard.

Screenshot 2025-06-01 173542.png

42 KiB

AnonSky added the

bug

label

2025-06-01 17:36:00 +02:00

AnonSky commented

2025-06-01 17:37:40 +02:00

Author

Actually it seems that most buttons don't work. I can't even save any modification I do to my logins. Buttons don't do anything. Working fine on Firefox Vanilla & Libre Wolf.

AnonSky changed title from ~~[BUG] PLEASE REPLACE THIS TEXT WITH A SUMMARY OF YOUR ISSUE...~~ to [BUG] Proton Pass not working as expected

2025-06-01 17:38:12 +02:00

celenity self-assigned this

2025-06-04 01:35:24 +02:00

celenity added the

confirmed

label

2025-06-04 02:08:50 +02:00

celenity commented

2025-06-04 02:11:10 +02:00

Owner

@AnonSky Thanks for the report, I was able to reproduce the issue. Setting extensions.webextensions.base-content-security-policy.v3 to script-src 'self' 'wasm-unsafe-eval'; upgrade-insecure-requests; in your about:config should take care of it. I went ahead and added it to the Web Compat page (even though isn't technically a website issue - I think this is still the best place to put this for the time being, until/if we come up with something better).

@AnonSky Thanks for the report, I was able to reproduce the issue. Setting `extensions.webextensions.base-content-security-policy.v3` to `script-src 'self' 'wasm-unsafe-eval'; upgrade-insecure-requests;` in your `about:config` should take care of it. I went ahead and added it to the [Web Compat page](https://phoenix.celenity.dev/compat) *(even though isn't technically a website issue - I think this is still the best place to put this for the time being, until/if we come up with something better)*.

🎉 1

celenity closed this issue

2025-06-04 02:11:14 +02:00