Bug 18488 - Cannot determine connection state of an AudioNode
Cannot determine connection state of an AudioNode
Status: CLOSED LATER
Product: AudioWG
Classification: Unclassified
Component: Web Audio API
unspecified
All All
: P2 major
: TBD
Assigned To: Chris Rogers
public-audio
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-08-04 14:31 UTC by Joe Berkovitz / NF
Modified: 2012-10-12 07:56 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Joe Berkovitz / NF 2012-08-04 14:31:18 UTC
The AudioNode interface doesn't allow one to discover its set of connected input and output AudioNodes (e.g. through readonly computed Array attributes like connectedInputNodes, connectedOutputNodes). This often requires a developer to separately track connection state in a way that feels unnecessarily complicated and is also error-prone.

Also, the inability to determine the set of connected nodes feels at odds with other web APIs in which modifications to an object's state can usually be read back.
Comment 1 Olivier Thereaux 2012-08-06 10:46:27 UTC
+1

This is related/equivalent to the recent discussion on the need for AudioContext introspection, for which there have been discussion on the group's list recently.

http://lists.w3.org/Archives/Public/public-audio/2012JulSep/0430.html
There have been other discussion on the list. Links TBA.
Comment 2 Olivier Thereaux 2012-09-28 10:15:08 UTC
Per http://www.w3.org/2012/09/26-audio-minutes#item04 the group decided that this was a feature which we should not focus on for the time being.
Comment 3 Olivier Thereaux 2012-10-12 07:56:03 UTC
No objection after close to 2 weeks. Closing.