Closed
Bug 584541
Opened 14 years ago
Closed 13 years ago
add global remote webgl killswitch
Categories
(Toolkit :: Blocklist Policy Requests, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: blizzard, Unassigned)
References
Details
(Whiteboard: [ddn])
Add option: WebGL Internets [x] On [ ] Off This is the nuclear option, of course, and we're unlikely to use it. But we should have the capability just in case.
Comment 1•14 years ago
|
||
what do you mean by "remote" kill switch? Let's say it's tied in with the blocklist. The fastest we'd get people updated is about a day, assuming we don't spend a day agonizing over whether whatever problem it is is worth using the creepy global killswitch. A simple pref, on the other hand, allows some users to flip it immediately when they hear the news, and we can ship an update that flips the pref default in fairly short order: about a day from when we decide, most users updated a day or two after that. We already have the pref "webgl.enabled_for_all_sites". I'd love to see some UI around prefs for advanced features like this, downloadable fonts, hardware acceleration, video, and similar (maybe a new pane in the "Advanced" category) but it seems a bit creepy to be controlling it remotely from Mozilla HQ.
Updated•13 years ago
|
Whiteboard: [ddn]
Comment 2•13 years ago
|
||
It's been 16 months since this bug was filed. Closing as incomplete.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → INCOMPLETE
Assignee | ||
Updated•8 years ago
|
Product: addons.mozilla.org → Toolkit
You need to log in
before you can comment on or make changes to this bug.
Description
•