I’ve been using a WebAudioPlayer on my WebPages to generate sounds, and it’s worked really well, except on one page in particular. If the user clicks on a button on that page, or manually causes a dialog to open, then the WebAudioPlayer works from that point on.
What is it about a button press or web dialog that causes a page to start behaving, and to allow the WebAudioPlayer to play as it should?
I’ve got WebAudioPlayer’s on all my pages, all triggered programmatically, but it’s only the page that has a ton of WebContainers on it that forces me to ‘interact’ with the page before the WebAudioPlayer functions properly. Thanks for any advice.
5 posts - 3 participants