You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Originally reported on W3C Bugzilla ISSUE-20728 Tue, 22 Jan 2013 10:32:53 GMT
Reported by Olivier Thereaux
Assigned to
From ROC:
“Is there a reason not to make the first parameter of AudioBufferSourceNode.start()/stop() optional? Seems like it would be convenient to have it just default to zero so authors could write "node.start()" to make it play "right now", and ditto for node.stop().”
-- http://lists.w3.org/Archives/Public/public-audio/2013JanMar/0175.html
We still need to decide whether it makes sense to adopt similar changes to the OscillatorNode, and also to the alternate names for these two node types.
From ROC:
“Is there a reason not to make the first parameter of AudioBufferSourceNode.start()/stop() optional? Seems like it would be convenient to have it just default to zero so authors could write "node.start()" to make it play "right now", and ditto for node.stop().”
-- http://lists.w3.org/Archives/Public/public-audio/2013JanMar/0175.html
Editor agreed: http://lists.w3.org/Archives/Public/public-audio/2013JanMar/0176.html
The text was updated successfully, but these errors were encountered: