createMediaElementSource
createMediaStreamDestination
createMediaStreamSource
The API's above shouldn't be in BaseAudioContext. Do we have any plans to remove them or standardize them anytime soon?
These APIs are standardized and should be in the AudioContext and not BaseAudioContext. We can't move these quite yet because we depend on being able to test these using an OfflineAudioContext.
No, that doesn't really make sense there because offline context run faster than real time and because CORS will prevent many uses of them because an offline context lets you get at the audio data.
This is something we need to fix but we need to get our layout tests running on bots have have real audio hardware.
If this is needed for our own testing, is there a sensible use case for web developers as well? Or is this taking some test-only code path that doesn't actually work in the end-user binary?
I think it's useful to have these on an offline context, but we never bothered to explain how that would work when the offline context can run much faster than real time and pulling on an audio tag faster than real time.
Currently, there is not test-only code path for these methods; it should work for anyone, taking into account the behavior isn't well-defined.
Comment 1 by rtoy@chromium.org
, Feb 28 2017