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

[web-audio-api] Cannot determine connection state of an AudioNode (#164)

From: Olivier Thereaux <notifications@github.com>
Date: Wed, 11 Sep 2013 07:28:46 -0700
To: WebAudio/web-audio-api <web-audio-api@noreply.github.com>
Message-ID: <WebAudio/web-audio-api/issues/164@github.com>
> Originally reported on W3C Bugzilla [ISSUE-18488](https://www.w3.org/Bugs/Public/show_bug.cgi?id=18488) Sat, 04 Aug 2012 14:31:18 GMT
> Reported by Joe Berkovitz / NF
> Assigned to 

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.

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

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:50:11 UTC