Setting AudioBufferSourceNode.buffer again after it has already been set to a non-null buffer is no longer allowed and will generate an exception. This feature was deprecated and is now being removed
Documentation
Specification
Status in Chromium
Removed (tracking bug) in:
- Chrome for desktop release 44
- Chrome for Android release 44
- Chrome for iOS release 44
- Android WebView release 44
Consensus & Standardization
After a feature ships in Chrome, the values listed here are not guaranteed to be up to date.
- No signal
- Shipped/Shipping
- No signal
- No signals
Owners
Last updated on 2020-11-09
Comments
Use counter metrics indicates that there was no usage of setting the buffer attribute more than once.