Intent to Implement and Ship: WebAudio: min/max attributes for AudioParams
Philip Jägenstedt
We do intend to ship. I forgot to add that to the subject line.On Wed, Apr 20, 2016 at 1:31 AM, Philip Jägenstedt <phi...@opera.com> wrote:Do you intent to do this behind a runtime flag? At least from a distance, the change looks small and safe enough that you might just want to ship it immediately?On Tue, Apr 19, 2016 at 11:09 PM, 'Raymond Toy' via blink-dev <blin...@chromium.org> wrote:--
Contact emails
rt...@chromium.org, hong...@chromium.org
Spec
http://webaudio.github.io/web-audio-api/#AudioParam
http://webaudio.github.io/web-audio-api/#attributes-5
Summary
Add min and max read-only attributes to each AudioParam to specify the nominal range for the AudioParam.
Motivation
The WebAudio spec recently decided to specify the nominal range for each AudioParam so that the behavior could be more precisely defined. To make it easier for developers to know what the limits are, min and max attributes are added to each AudioParam to expose these limits. Without these, the developer must look up the relevant section of the spec and determine them himself.
Interoperability and Compatibility Risk
As part of the WebAudio API, we expect all browsers to implement this.
Ongoing technical constraints
None
Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
Yes.
OWP launch tracking bug
Link to entry on the feature dashboard
https://www.chromestatus.com/features/5693824068222976
Requesting approval to ship?
Yes
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
