proposed shortname + accessibility considerations (Bugzilla 17699, 17697)
authorOlivier Thereaux <Olivier.Thereaux@bbc.co.uk>
Mon, 03 Sep 2012 14:15:43 +0100
changeset 1562a6431dcb680
parent 155 9d14e0e3a3a6
child 157 bf0e920450e6
proposed shortname + accessibility considerations (Bugzilla 17699, 17697)
reqs/Overview.html
     1.1 --- a/reqs/Overview.html	Thu Aug 30 10:57:59 2012 -0400
     1.2 +++ b/reqs/Overview.html	Mon Sep 03 14:15:43 2012 +0100
     1.3 @@ -29,7 +29,7 @@
     1.4            specStatus:           "ED",
     1.5            
     1.6            // the specification's short name, as in http://www.w3.org/TR/short-name/
     1.7 -          shortName:            "audioproc-reqs",
     1.8 +          shortName:            "webaudio-usecases",
     1.9  
    1.10            // if your specification has a subtitle that goes below the main
    1.11            // formal title, define it here
    1.12 @@ -40,7 +40,7 @@
    1.13  
    1.14            // if the specification's copyright date is a range of years, specify
    1.15            // the start date here:
    1.16 -          copyrightStart: "2011",
    1.17 +          copyrightStart: "2012",
    1.18  
    1.19            // if there is a previously published draft, uncomment this and set its YYYY-MM-DD date
    1.20            // and its maturity status
    1.21 @@ -387,12 +387,14 @@
    1.22        
    1.23    
    1.24        
    1.25 -      <h3>User Control of Audio </h3>
    1.26 -      <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.
    1.27 -      </p>
    1.28 +      <h3>User Control of Audio</h3>
    1.29 +      <p>A programmer wants to create a browser extension to allow the user to control the volume of audio.</p> 
    1.30 +      <p>The extension should let the user control the audio volume on a per-tab basis, or to kill any audio playing completely. The extension developer wishes to make sure killing the audio is done in a way that takes care of garbage collection.</p>
    1.31 +      <p>Among the features sometimes requested for his extension are the ability to limit the audio volume to an acceptable level, both per tab and globally. On operating systems that allow it, the developer would also like his extension to mute or pause sound when a critical system sound is being played.</p>
    1.32        <h4>Notes and Implementation Considerations</h4>
    1.33        <ol>
    1.34 -        <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>
    1.35 +        <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>
    1.36 +        <li><p>The ability to mute or pause sounds when the Operating System fires a critical system sound is modelled after the feature in existing Operating Systems which will automatically mute applications when outputting a system sound. As such, this may not involve any specific requirement for the Web Audio API. However, because some operating systems may implement such a feature, Web Audio apps may want to be notified of the muting and act accordingly (suspend, pause, etc). There may therefore be a requirement for the Web Audio API to provide such an event handler.</p></li> 
    1.37        </ol>
    1.38      </section>
    1.39