We need to add support for a webgl blacklist and possibly a whitelist as well. Depends on the implementation inside of Firefox - i.e. if we have an explicit whitelist or blacklist for people to use to enable and disable webgl.
Oops, sorry I meant "permissions.sqlite", I got those mixed up.
Wait, the word "remote" here is throwing me off -- we need to add support for a webgl enabled/disabled per-site capability. But not one that we want to manage or serve remotely; it should be similar to "is this site allowed to load images" or "is this site allowed to use geolocation".
If that's the case, this bug probably shouldn't be in the AMO Blocklisting component.
I kind of agree here -- we shouldn't have a site blocklist for this. Malicious sites can be handled by safe browsing. So -> WONTFIX; object if you have objections.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
is there a different bug for an in-product (permission manager?) whitelist/blacklist for WebGL? Do we have it already?
Product: addons.mozilla.org → Toolkit
Could this be reconsidered? I find a whitelist would be extremely beneficial in terms of both privacy and security. WebGL is incredibly useful as a web technology but can cause plethora of different issues, as previously mentioned, a whitelist would allow giving access to webgl functionality only to those websites that are utilizing it with a use for the person using the browser. This would also mean people browsing on battery power do not have to worry about their GPU spinning up because some tracking script or ad network decided to render something.
You need to log in before you can comment on or make changes to this bug.