Add explanatory notes to User Control of Audio scenario explaining interplay between extension APIs (to enumerate windows) and unimplemented Web Audio API touch points to control volume on a window by window basis.
authorJoe Berkovitz <joe@noteflight.com>
Wed, 22 Aug 2012 14:10:29 -0400
changeset 140 974c1ceb8f93
parent 139 564e65c76380
child 141 c1212826d4fd
Add explanatory notes to User Control of Audio scenario explaining interplay between extension APIs (to enumerate windows) and unimplemented Web Audio API touch points to control volume on a window by window basis.
reqs/Overview.html
--- a/reqs/Overview.html	Wed Aug 22 14:00:16 2012 -0400
+++ b/reqs/Overview.html	Wed Aug 22 14:10:29 2012 -0400
@@ -360,6 +360,10 @@
       <h3>User Control of Audio </h3>
       <p>A programmer wants to create a browser extension to allow the user to control the volume of audio on a per-tab basis, or to kill any audio playing completely, in a way that takes care of garbage collection.
       </p>
+      <h4>Notes and Implementation Considerations</h4>
+      <ol>
+        <li><p>This function is likely to combine usage of both a browser-specific extension API and the Web Audio API. One way to implement this scenario would be to use a browser-dependent API to iterate through a list of window objects, and then for each window object iterate through a list of active AudioContexts and manage their volume (or, more conveniently, manage some kind of master audio volume for the window). Neither of these latter approaches are currently supported by the Web Audio API</p></li>
+      </ol>
     </section>
     
     <section>