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

[Bug 17795] Behavior of multiple connections to same node needs to be explicitly defined

From: <bugzilla@jessica.w3.org>
Date: Thu, 19 Jul 2012 16:37:30 +0000
Message-Id: <E1SrtjG-0003gM-UG@jessica.w3.org>
To: public-audio@w3.org

--- Comment #5 from Robert O'Callahan (Mozilla) <roc@ocallahan.org> 2012-07-19 16:37:30 UTC ---
> > Imagine if some module builds an AudioNode A, and then two other modules
> > independently get hold of A and try to play it by connecting it to the
> > DestinationNode. It would be confusing to have one of those operations
> > unexpectedly fail.
> I'm not suggesting at all that it WOULD fail.  It doesn't today - it just
> doesn't create an ADDITIONAL, duplicate connection (thereby doubling the gain,
> which would be just as unpredictable, and IMO less usable.)

Depends on your point of view I guess. In this case I think the author would
expect connect() to cause a change in the output, and it won't.

Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Thursday, 19 July 2012 16:37:35 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:03:10 UTC