[followup] crypto.getRandomValues should also accept an ArrayBuffer as an argument

RESOLVED INVALID

Status

()

Core
Security: PSM
RESOLVED INVALID
6 years ago
5 years ago

People

(Reporter: ddahl, Assigned: ddahl)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(Assignee)

Description

6 years ago
(Getting this requirement 2nd hand)

The DOM API team would prefer all DOM APIs that use TypedArrays to use basic ArrayBuffers instead of ArrayBuffer Views. 

Opening this bug to allow for the small patch that would allow this change.

This is also a good place to discuss the reasons why we should not use views and only use plain ArrayBuffers.
(Assignee)

Updated

6 years ago
Depends on: 440046
(Assignee)

Updated

6 years ago
Assignee: nobody → ddahl
(Assignee)

Comment 1

5 years ago
I am pretty sure this is INVALID at this point. See the spec: https://dvcs.w3.org/hg/webcrypto-api/raw-file/tip/spec/Overview.html#RandomSource-method-getRandomValues
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.