[web-audio-api] AudioNode.disconnect() needs to be able to disconnect only one connection (#6)

> Originally reported on W3C Bugzilla [ISSUE-17793](https://www.w3.org/Bugs/Public/show_bug.cgi?id=17793) Tue, 17 Jul 2012 18:30:24 GMT
> Reported by Chris Wilson
> Assigned to 

(Summary of email conversation in list)

There is currently no way to disconnect node A's connection to node B without disconnecting all connections from node A to other nodes.  This makes it impossible to disconnect node B from the graph without potential side effects, as you have to:

- call disconnect() on node A (which disconnects all its outputs)
- reconnect every connection that node A used to have, EXCEPT the connection to node B.

Not only is this cumbersome, it will be problematic in the future when we solve the related issue of unconnected streams - which is currently exhibiting incorrect behavior in Chrome (it pauses the audio stream), but is underspecified in the spec today.  (filing separate bug).  Disconnecting then reconnecting would have to have no side effects.  (It works okay today, but not ideal - can click.)

Recommended solution:
- there should be a way to remove a single connection (by supplying the destination node to be disconnected, since there can only be one connection to a given destination node [tested]).

E.g.: the IDL for disconnect should read:

        void disconnect(in [Optional] AudioNode destination, in [Optional] unsigned long output = 0)
            raises(DOMException);

this lets us keep most compatibility - node.disconnect() will still remove all connections.

---
Reply to this email directly or view it on GitHub:
https://github.com/WebAudio/web-audio-api/issues/6