ISSUE-72: (Bugzilla 17359) ConvolverNode state modification


(Bugzilla 17359) ConvolverNode state modification

Web Audio API
Raised by:
Philip J├Ągenstedt
Opened on:
When buffer and normalize are modified, when does it take effect? If modifications are not applied atomically, it's possible to get spikes (or dropouts) depending on the order of setting and the previous state.


Further, setting normalize to true is defined using the phrasing "when the buffer atttribute is set", which implies that the order of setting the attributes matters. However, no such order-dependence exists when setting normalize to false.

If an order-dependence is intended, it ought to be changed to either commit atomically after the script thread has finished, or we should have a setter taking both a buffer and a normalize flag.
Related Actions Items:
No related actions
Related emails:
  1. [web-audio-api] (ConvolverNodeState): ConvolverNode state modification (#122) (from on 2013-09-11)
  2. Re: Summary of issues (from on 2012-05-22)
  3. Summary of issues (from on 2012-05-22)
  4. Audio-ISSUE-72 (ConvolverNodeState): ConvolverNode state modification [Web Audio API] (from on 2012-05-16)

Related notes:


5 Jun 2012, 13:45:32

Display change log ATOM feed

Matthew Paradis <>, Raymond Toy <>, Chairs, Chris Lilley <>, Staff Contact
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <>.
$Id: 72.html,v 1.1 2019/11/12 13:32:40 carcone Exp $