18488 2012-08-04 14:31:18 +0000 Cannot determine connection state of an AudioNode 2012-10-12 07:56:03 +0000 1 1 1 Unclassified AudioWG Web Audio API unspecified All All CLOSED LATER P2 major TBD 1 joe crogers olivier.thereaux public-audio oldest_to_newest 71840 0 joe 2012-08-04 14:31:18 +0000 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. 71850 1 olivier.thereaux 2012-08-06 10:46:27 +0000 +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. 74770 2 olivier.thereaux 2012-09-28 10:15:08 +0000 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. 76068 3 olivier.thereaux 2012-10-12 07:56:03 +0000 No objection after close to 2 weeks. Closing.