Bug 17343 - (AudioBufferSourceNodeState): AudioBufferSourceNode state semantics and transitions undefined
Summary: (AudioBufferSourceNodeState): AudioBufferSourceNode state semantics and trans...
Status: CLOSED FIXED
Alias: None
Product: AudioWG - OBSOLETE - Moved to Github
Classification: Unclassified
Component: Web Audio API - OBSOLETE - See Github (show other bugs)
Version: unspecified
Hardware: PC Windows 3.1
: P2 normal
Target Milestone: TBD
Assignee: Chris Rogers
QA Contact: public-audio
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-06-05 11:35 UTC by Philip Jägenstedt
Modified: 2013-05-14 10:25 UTC (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Philip Jägenstedt 2012-06-05 11:35:24 UTC
Audio-ISSUE-51 (AudioBufferSourceNodeState): AudioBufferSourceNode state semantics and transitions undefined [Web Audio API]

http://www.w3.org/2011/audio/track/issues/51

Raised by: Philip Jägenstedt
On product: Web Audio API

The meaning of each state is undefined, implied only by their name.

It is not defined when state transitions happen. For example, does playbackState change synchronously in the note* calls, or are the operations scheduled for later?

Related to https://www.w3.org/2011/audio/track/issues/28
Comment 1 Chris Rogers 2013-04-29 23:35:08 UTC
As discussed, the .playbackState attribute and its associated constants are being removed:
https://dvcs.w3.org/hg/audio/rev/37459e013fce
Comment 2 Olivier Thereaux 2013-05-14 10:25:00 UTC
The resolution seems acceptable to the group. Closing.