This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 24409 - Consider making BigInteger an ArrayBuffer
Summary: Consider making BigInteger an ArrayBuffer
Status: RESOLVED WONTFIX
Alias: None
Product: Web Cryptography
Classification: Unclassified
Component: Web Cryptography API Document (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Ryan Sleevi
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-27 16:39 UTC by Mark Watson
Modified: 2014-01-28 19:06 UTC (History)
3 users (show)

See Also:

Attachments

Description Mark Watson 2014-01-27 16:39:38 UTC 
There's no reason to specify Unit8Array - the application may want to manipulate this using some other TypedArray. As far as the API is concerned it's an integer expressed in big-endian binary.
Comment 1 Alexey Proskuryakov 2014-01-27 17:28:24 UTC 
What are the use cases that are currently not well served with current API? It is trivial to get a view of a different type when needed:

new Uint32Array(myUint8View.buffer);

I suggest WONTFIX resolution for this bug, as the current solution works well.
Comment 2 Franz Antesberger 2014-01-28 18:35:28 UTC 
new Uint32Array(myUint8View.buffer);
will only work, if the buffer length is a multiple of 4.

But I agree, we have no advantage of ArrayBuffer (even if I suggested it, originally).
+1 for WONTFIX