We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Originally reported on W3C Bugzilla ISSUE-17381 Tue, 05 Jun 2012 12:02:23 GMT Reported by Philip Jägenstedt Assigned to
Audio-ISSUE-97 (EventScheduling): Event Scheduling ("Need more detail here") [Web Audio API]
http://www.w3.org/2011/audio/track/issues/97
Raised by: Philip Jägenstedt On product: Web Audio API
https://dvcs.w3.org/hg/audio/raw-file/tip/webaudio/specification.html#EventScheduling
It looks like this section is intended to talk about scheduling of AudioParam value changes and possibly note* in AudioBufferSourceNode.
Since the section currently doesn't say anything, we suggest dropping it and expanding on the relevant sections.
The text was updated successfully, but these errors were encountered:
Original comment by Chris Rogers on W3C Bugzilla. Fri, 05 Oct 2012 21:30:28 GMT
Fixed, section removed as suggested: https://dvcs.w3.org/hg/audio/rev/2246b4813c5a
Sorry, something went wrong.
Original comment by Philip Jägenstedt on W3C Bugzilla. Mon, 08 Oct 2012 09:04:01 GMT
Looks good.
(This should have been set as closed).
No branches or pull requests
Audio-ISSUE-97 (EventScheduling): Event Scheduling ("Need more detail here") [Web Audio API]
http://www.w3.org/2011/audio/track/issues/97
Raised by: Philip Jägenstedt
On product: Web Audio API
https://dvcs.w3.org/hg/audio/raw-file/tip/webaudio/specification.html#EventScheduling
It looks like this section is intended to talk about scheduling of AudioParam value changes and possibly note* in AudioBufferSourceNode.
Since the section currently doesn't say anything, we suggest dropping it and expanding on the relevant sections.
The text was updated successfully, but these errors were encountered: