On Friday, May 24, 2013 5:11:25 PM UTC+1, Kevin Reid wrote: > > On Fri, May 24, 2013 at 4:02 AM, Cristiano Belloni > <[email protected]<javascript:> > > wrote: > >> Hi all, is there a way to pass the guest page an Audio API >> context<https://dvcs.w3.org/hg/audio/raw-file/tip/webaudio/specification.html>object? >> It seems taming a context return undefined. Sample example >> here <https://dl.dropboxusercontent.com/u/6767816/testcajahost.html>, >> tamedContext gets undefined.. >> >> (as a total Caja newbie, this is more a way to learn why not and getting >> the hang of it by trying doing things, so pease be pedantic). >> > > Caja does not include a taming of the Web Audio API. > > There's no reason not to (except that we would have to give the host page > a way to control audio input/output access), but it hasn't previously come > up on our list of APIs people want. >
Where's that list? I would gladly add that request :) (the final goal is to load throught Caja unsafe plugins in this project of mine: http://kievii.net/k2h.html). I agree that the host page would have a way to control audio source and audioDestination. > > You could try simply using the available taming membrane controls to allow > a context to be passed into the guest — you would have to explicitly mark > as safe every part of the API you use. I don't offhand see any reason why > that wouldn't work. > How would I do that in practice? Taming the Web Audio api functions inside the context object? -- --- You received this message because you are subscribed to the Google Groups "Google Caja Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
