Re: [web-audio-api] (NoteOnOffInteraction): noteOn and noteOff (start and stop) interaction (#126)

> [Original comment](https://www.w3.org/Bugs/Public/show_bug.cgi?id=17402#2) by Olivier Thereaux on W3C Bugzilla. Thu, 07 Jun 2012 15:01:21 GMT

More feedback from Philip in http://lists.w3.org/Archives/Public/public-audio/2012AprJun/0432.html

«
We'd prefer if the conditions were defined strictly in terms of  
playbackState.

Suggested phrasing for noteOn: "If playbackState is not UNSCHEDULED_STATE,  
then the user agent must throw an InvalidStateError exception. Set  
playbackState to SCHEDULED_STATE."

Suggested phrasing for noteOff: "If playbackState is UNSCHEDULED_STATE,  
then the user agent must throw an InvalidStateError exception." followed  
by the steps to schedule a playback stop.

As you can tell, we don't think there's any point in disallowing multiple  
calls to noteOff. If we want to disallow it, a new playbackState will be  
needed. One can of course implement a hidden state, but it seems simpler  
and better to make readyState match reality.
»

---
Reply to this email directly or view it on GitHub:
https://github.com/WebAudio/web-audio-api/issues/126#issuecomment-24244361