W3C home > Mailing lists > Public > public-audio@w3.org > July to September 2013

[web-audio-api] It is not exact to describe stop function of AudioBufferSourceNode (#15)

From: Olivier Thereaux <notifications@github.com>
Date: Wed, 11 Sep 2013 07:27:38 -0700
To: WebAudio/web-audio-api <web-audio-api@noreply.github.com>
Message-ID: <WebAudio/web-audio-api/issues/15@github.com>
> Originally reported on W3C Bugzilla [ISSUE-20229](https://www.w3.org/Bugs/Public/show_bug.cgi?id=20229) Tue, 04 Dec 2012 08:46:43 GMT
> Reported by Li Yin
> Assigned to 

>From the spec, it says "stop must only be called one time and only after a call to start or stop, or an exception will be thrown."

It's confused to me that if stop can be called only one time, it should be impossible that stop can be called after stop. In offlinemode, stop can be called multiple times from web developers' eyes.

So maybe it will be more reasonable if we describe it like this:
start can be called only when playbackState is UNSCHEDULED_STATE, or InvalidStateError exception will be thrown.
stop can be called only when playbackState is SCHEDULED_STATE or PLAYING_STATE, if not, InvalidStateError exception will be thrown.

---
Reply to this email directly or view it on GitHub:
https://github.com/WebAudio/web-audio-api/issues/15
Received on Wednesday, 11 September 2013 14:29:05 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:03:24 UTC