Skip to content
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

Figma cursors appear to be corrupt on dot browser #80

Open
2 tasks done
trickypr opened this issue Apr 4, 2021 · 2 comments
Open
2 tasks done

Figma cursors appear to be corrupt on dot browser #80

trickypr opened this issue Apr 4, 2021 · 2 comments
Labels
bug Something isn't working

Comments

@trickypr
Copy link
Contributor

trickypr commented Apr 4, 2021

Preflight Checklist

  • I have read the Contributing Guidelines for this project.
  • I have searched the issue tracker for an issue that matches the one I want to file, without success.

Component
privacy.resistFingerprinting

Describe the bug
When using figma, large parts of the site display in a way that looks like there is serious corruption happening.

To Reproduce
Steps to reproduce the behavior:

  1. Go to Figma
  2. Click on open this file: https://www.figma.com/file/v0LYuyR8nkhrqNbesl5cyT/DotHQ?node-id=0%3A1
  3. Observe

Expected behavior
This should render as it does on regular firefox

Screenshots
Screenshot from 2021-04-04 17-13-43

System Information (please complete the following information):

  • OS: Manjaro
  • Version: idk

Dot Browser Information (please complete the following information):

  • Version: Nightly 87.0-715616008
  • Site you were on before the bug appeared: Figma

Additional context
A canvas security popup appeared, I do not know if that is in any way related. This doesn't appear to be present on ff nightly.

@trickypr trickypr added the bug Something isn't working label Apr 4, 2021
@trickypr
Copy link
Contributor Author

trickypr commented Apr 4, 2021

So, I have dug deeper into this and it is a result of the canvas protection popup. When clocking "Allow Data Access" it doesn't fix the page immediately, but it fixes the page after a reload.
image
A simple solution to this would be to reload the page if the user accepts.

Update
This issue is present on regular firefox as well. If you enable the privacy.resistFingerprinting flag, you will experience the same behavior.

@mugman174
Copy link

mugman174 commented May 19, 2021

I experience this with many other websites, like the QR code login feature of Discord, and Element.

broken discord qr code
It works when I allow the website to use my HTML5 canvas image data.

@kierandrewett kierandrewett transferred this issue from dothq/browser Sep 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants