-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uploading images with firefox are broken with resistfingerprinting=true #13582
Comments
Thanks for the link and info, however My mind have already been in that direction, as I uses So have disabled all add-ons and restarted the browser for testing, and yes I do have the fingerPrinting enabled as default, but this should be overwritten by the domain specific rules "EnableTrackingProtection": {
"Value": true,
"Locked": false,
"Cryptomining": true,
"Fingerprinting": true,
"EmailTracking": true
}, |
Did you still see the problem after that? You can also try Troubleshoot Mode in about:support. |
Alright, I can repro this with any PNG upload. Maybe this is related to OffscreenCanvas use? Would you mind filing an issue in https://bugzilla.mozilla.org/ and link back here? |
Kinda, As I have no intention to give them any of my mail addresses. But please do feel free to do so on my behalf. A little side note: The problem also relates to |
Just found https://bugzilla.mozilla.org/show_bug.cgi?id=1422862 and added this issue there. |
and then we wait yet another year on a solution to a "major" problem.... Thanks for committing the issue |
💡 Summary
Every time I try to add a image to a post by either upload or copy/paste, the images are broken, but if I uses a different browser, things goes well.
However, when I uses the
From uri
the image are upload as supposed.🥰 Expected Behavior
The images should in this text show the BSD devil
🤬 Actual Behavior
The images looks like this
https://matrix.rocks/files/18f75b42-d514-4d99-a184-93bfd48e6a92
📝 Steps to Reproduce
💻 Frontend Environment
🛰 Backend Environment (for server admin)
Do you want to address this bug yourself?
The text was updated successfully, but these errors were encountered: