Skip to content
New issue

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

Change the MIDIOutput.send() spec to allow raising a RangeError when the passed ArrayBuffer is too big #210

Open
toyoshim opened this issue Dec 17, 2019 · 2 comments
Labels
class: substantive https://www.w3.org/2023/Process-20230612/#correction-classes status: ready for editing Enough information should be available to implement this change in the spec
Milestone

Comments

@toyoshim
Copy link
Contributor

Now Chrome is going to support very large ArrayBuffers that can exceed 4GB, and it isn't realistic to handle such large ArrayBuffers correctly when it is passed via MIDIOutput.send().

So, it would be nicer that the UA can raise RangeError if the passed ArrayBuffer is too large to handle efficiently.

https://webaudio.github.io/web-midi-api/#midioutput-interface
There are two "If data is ... " conditions. So, we would add one more,

If data is too large to handle efficiently, throw a RangeError exception.

@toyoshim
Copy link
Contributor Author

@cwilso cwilso added this to the V1 milestone Oct 12, 2020
@mjwilson-google mjwilson-google added the class: substantive https://www.w3.org/2023/Process-20230612/#correction-classes label Sep 13, 2023
@mjwilson-google mjwilson-google added the status: needs WG review Needs to be discussed with the Audio Working Group before proceeding label Sep 30, 2023
@mjwilson-google
Copy link
Contributor

Audio Working Group 2023-10-05 meeting conclusions:

@mjwilson-google mjwilson-google added status: ready for editing Enough information should be available to implement this change in the spec and removed status: needs WG review Needs to be discussed with the Audio Working Group before proceeding labels Oct 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
class: substantive https://www.w3.org/2023/Process-20230612/#correction-classes status: ready for editing Enough information should be available to implement this change in the spec
Projects
None yet
Development

No branches or pull requests

3 participants