-
Notifications
You must be signed in to change notification settings - Fork 57
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
Accept shared ArrayBufferView also? #213
Comments
Jimmy, do you have a plan for getting some browser implementors engaged in discussion here about this proposal? |
not really |
OK, then unless there’s somebody else who weighs in on this relatively soon with some plan, I’m gonna propose that we close this |
Today i tried to use BigUint64Array with I think some web crypto stuff have fallen behind since we have got new types of array's (big int, sharedArrayBuffer etc) crypto.getRandomValues(new BigUint64Array(1))
BigUint64Array is a ArrayBufferView so it should work imo. Looking at the spec then it looks to be somewhat outdated... and don't seem to be a specific browser issue.
Why should it be just dose types? I think it should be changed to something like eg: |
Now we have a new error calling Crypto.getRandomValues() backed by a SharedArrayBuffer. See: w3c/webcrypto#213
I tried to use shared ArrayBuffer view along with crypto api. Didn't work
Is there any reason why it would not be allowed? didn't find any issue or text in the spec mention anything about sharedArrayBuffer
The text was updated successfully, but these errors were encountered: