Primary eng (and PM) emails
rt...@chromium.org, hong...@chromium.org
Link to “Intent to Deprecate” thread
https://groups.google.com/a/chromium.org/d/msg/blink-dev/9-ZId2s0cvw/7BRdlEeqpfgJ
Summary
Give a high-level description of your change. (Fine to copy/paste from “Intent to Deprecate” thread.)
Motivation
We deprecated setting the AudioBufferSourceNode.buffer more than once several months ago and targeted M43 for removal. M43 is beta now, we intend to remove it in M44.
From the deprecation thread:
Allowing the user to set the AudioBufferSourceNode buffer attribute multiple times has issues:
Usage information from UseCounter
According to the UseCounter for AudioBufferSourceBufferOnce, there is no usage of this.
Entry on chromestatus.com
No entry yet on chromestatus, but the entry for deprecation exists.
Compatibility Risk
There is some compatibility risk since this ability was allowed. However, based on the UseCounter metrics, it's very uncommon. Currently all browers support setting the buffer more than once. However, the WebAudio spec does not allow the buffer to be set again after it has already been set. We believe FireFox will disallow setting the buffer more than once.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
Can you also add the removal to Chromestatus.com so that it appears in https://www.chromestatus.com/features#removed, we are trying to make it easier for developers to find and be aware of breaking features.