This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
http://www.w3.org/2011/audio/track/issues/15 Raised by: Jer Noble On product: Web Audio API On the mailing list, Jer Noble proposed an addition to the WebAudio API which would allow the API to be implemented on platforms which allow exclusive access to audio hardware. http://lists.w3.org/Archives/Public/public-audio/2012AprJun/0122.html The proposed changes: * Add the AudioContext.startRendering() method to the spec. * Add a new AudioContext.renderState property to the spec. + Values: - RENDERING - INTERRUPTED - IDLE Chris Rogers questioned why the startRendering() method was necessary: http://lists.w3.org/Archives/Public/public-audio/2012AprJun/0124.html Jer Noble replied with a use case demonstrating its use: http://lists.w3.org/Archives/Public/public-audio/2012AprJun/0126.html
Jer, is this something you still believe is important to consider? I know iOS has been shipping for a little while and didn't know if this was still an issue.
Yes I believe it is still an issue. It's unfortunate that we weren't able to resolve this prior to iOS 6, but I believe this is still important to resolve for future implementations.
Web Audio API issues have been migrated to Github. See https://github.com/WebAudio/web-audio-api/issues
Closing. See https://github.com/WebAudio/web-audio-api/issues for up to date list of issues for the Web Audio API.