Re: MediaElementAudioSource / MediaStreamAudioSource for offlineAudioContext

On Mon, Feb 17, 2014 at 4:20 AM, Chris Lowis <chris.lowis@gmail.com> wrote:

> There’s an action[1] on me to take a look at the issue raised last year[2]
> about how/whether the following methods should be defined on instances of
> offlineAudioContext:
>
> createMediaElementSource
> createMediaStreamSource
> createMediaStreamDestination
>
> At the moment offlineAudioContext is defined as a subclass of
> AudioContext. One option therefore is to override these methods to raise
> some kind of “unsupported” exception when called on an instance of
> offlineAudioContext. This doesn’t feel right to me. It’d be nicer if they
> simply didn’t exist on offlineAudioContext.
>

None of the options here are ideal, but I don't think we should make a
breaking change. That seems unnecessary for feels like a minor cosmetic
blemish to me.

A non-breaking, less-ugly approach would be to move most of AudioContext to
a new interface AudioContextBase (or something like that), and have
OfflineAudioContext and AudioContext both inherit from it.

Rob
-- 
Jtehsauts  tshaei dS,o n" Wohfy  Mdaon  yhoaus  eanuttehrotraiitny  eovni
le atrhtohu gthot sf oirng iyvoeu rs ihnesa.r"t sS?o  Whhei csha iids  teoa
stiheer :p atroa lsyazye,d  'mYaonu,r  "sGients  uapr,e  tfaokreg iyvoeunr,
'm aotr  atnod  sgaoy ,h o'mGee.t"  uTph eann dt hwea lmka'n?  gBoutt  uIp
waanndt  wyeonut  thoo mken.o w