This repository has been archived by the owner on Dec 11, 2019. It is now read-only.
Include "Block HTML canvas and WebGL fingerprinting" into Bravery Panel #1876
Labels
design
A design change, especially one which needs input from the design team.
feature/shields
suggestion
Milestone
Describe the issue you encountered: Sometimes it is hard to detect the issue, when the site does not work as it should, because of blocking the HTML canvas and WebGL fingerprinting. In my case, adding a macro at Zendesk.
Expected behavior: Display a toggle to enable/disable them, next to the "Block phising / malware"
If it is hard to difficult to implement it like this (blocking them needs to be a global config, for example) , something which indicates that they were blocked, like the NoScript icon, would help users to understand what is going on. Currently they have to open devtool and check out the output on the console.
The text was updated successfully, but these errors were encountered: