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

Specification link


Specification being incubated in a Community Group

Status in Chromium

Blink


Removed (tracking bug)

Consensus & Standardization

After a feature ships in Chrome, the values listed here are not guaranteed to be up to date.

  • No signal
  • No signal
  • No signals

Owners

Comments

Use counter metrics indicates that there was no usage of setting the buffer attribute more than once.

Last updated on 2021-05-05