Bug 19766: Clarify that reading AudioParam.computedValue will return the latest computed value for the latest audio quantum
--- a/webaudio/specification.html Tue Nov 13 15:47:25 2012 -0800
+++ b/webaudio/specification.html Tue Nov 13 16:02:50 2012 -0800
@@ -1523,7 +1523,14 @@
</li>
</ol>
-
+ </p>
+
+ <p>
+ The <em>computedValue</em> is constantly being updated by the audio rendering thread at each rendering time quantum.
+ Thus when the main JavaScript thread reads this value, then it will reflect the latest computed value.
+ This will mean that reading computedValue twice in a row will potentially return different results
+ if the audio thread's computations have changed the computed value of an AudioParam. This is similar to how
+ calling <code>performance.now()</code> will return an different up-to-date high-resolution time if called two times in a row.
</p>
</dd>
</dl>