Closed
Bug 788310
Opened 12 years ago
Closed 12 years ago
Hide mozAudioContext behind a pref
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
FIXED
mozilla18
People
(Reporter: ehsan.akhgari, Assigned: ehsan.akhgari)
References
Details
Attachments
(1 file)
5.67 KB,
patch
|
bzbarsky
:
review+
|
Details | Diff | Splinter Review |
Seems like there are people who test for mozAudioContext for forward compatibility (which is a sane thing to do), and we are breaking them! We need to fix that. Boris, is the right thing to do here returning null from AudioContext::Construct? How can I make sure that tests for the existence of mozAudioContext would fail as well?
Comment 1•12 years ago
|
||
The right thing to do is probably to wait until I fix bug 778044 (which should be very shortly), and then make use of that.
Depends on: 778044
Updated•12 years ago
|
OS: Mac OS X → All
Hardware: x86 → All
Assignee | ||
Comment 2•12 years ago
|
||
Comment 3•12 years ago
|
||
Comment on attachment 659372 [details] [diff] [review] Patch (v1) r=me, though if we're going to pref this off why not drop the "moz" from the name?
Attachment #659372 -
Flags: review?(bzbarsky) → review+
Assignee | ||
Comment 4•12 years ago
|
||
(In reply to Boris Zbarsky (:bz) from comment #3) > Comment on attachment 659372 [details] [diff] [review] > Patch (v1) > > r=me, though if we're going to pref this off why not drop the "moz" from the > name? The Web Audio spec is not stable yet, and also we're probably not going to implement all of the spec initially, so I would prefer us to keep this prefixed until we are sure that the API won't change and our implementation matches the spec.
Assignee | ||
Comment 5•12 years ago
|
||
http://hg.mozilla.org/integration/mozilla-inbound/rev/898df3138008
Flags: in-testsuite+
Target Milestone: --- → mozilla18
Comment 6•12 years ago
|
||
https://hg.mozilla.org/mozilla-central/rev/898df3138008
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•5 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•