Closed
Bug 1305100
Opened 9 years ago
Closed 9 years ago
Remove the dom.webaudio.enabled pref
Categories
(Core :: Web Audio, defect, P2)
Core
Web Audio
Tracking
()
RESOLVED
INVALID
People
(Reporter: ehsan.akhgari, Unassigned)
Details
Attachments
(1 file)
|
23.31 KB,
patch
|
baku
:
review+
|
Details | Diff | Splinter Review |
This pref was used when developing the Web Audio feature. Since this
feature is now an established part of the Web platform, we don't need to
continue support disabling it at runtime.
|
Reporter | |
Comment 1•9 years ago
|
||
Attachment #8794306 -
Flags: review?(padenot)
Attachment #8794306 -
Flags: review?(amarchesini)
|
||
Updated•9 years ago
|
Attachment #8794306 -
Flags: review?(amarchesini) → review+
|
||
Updated•9 years ago
|
Rank: 25
Priority: -- → P2
|
||
Comment 2•9 years ago
|
||
Ehsan, Andrea, see bug 1288359. This is very recent and has been implemented after reading about a proof of concept of a quite effective fingerprinting technique using the Web Audio API.
We don't know yet how to be more robust against this fingerprinting technique (because of the lack of time to study their code), but we wanted to address this so that people that have particular needs can still use Firefox (or something like the Tor browser), at the expense of not being perfectly web-compatible. I suppose that not being to synthesize and filter audio is okay in this case.
The Web Audio API is still enabled by default of course.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → INVALID
|
|
||
Updated•9 years ago
|
Attachment #8794306 -
Flags: review?(padenot)
You need to log in
before you can comment on or make changes to this bug.
Description
•