- From: <bugzilla@jessica.w3.org>
- Date: Mon, 12 May 2014 03:54:59 +0000
- To: public-webcrypto@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25658 Bug ID: 25658 Summary: Need normative reference for ArrayBufferView type Product: Web Cryptography Version: unspecified Hardware: PC OS: All Status: NEW Severity: blocker Priority: P2 Component: Web Cryptography API Document Assignee: sleevi@google.com Reporter: sleevi@google.com CC: public-webcrypto@w3.org The handling of the various typed arrays has moved from the Kronos specification ( https://www.khronos.org/registry/typedarray/specs/latest/ ) into being part of ES6 proper ( http://people.mozilla.org/~jorendorff/es6-draft.html ) During the W3C TAG review, it was highlighted that the normative references for Typed Arrays should be updated to refer to the ES6 specification. Within ES6, the ArrayBuffer object family still exists. However, the notion of ArrayBufferView has been subsumed into the pseudo-object %TypedArray%, along with concrete instances of it (eg: UInt8Array). The result of this is that it's no longer linguistically possible to refer to "an ArrayBufferView" within the specification. Instead, the closest approximation would appear to be "an object whose Type(object) is Object and which has a [[TypedArrayName]] internal slot whose value is not undefined" The interim solution will be to continue to refer to "ArrayBufferView", as if it were a discrete type. However, this will likely prevent the document from entering REC track until suitable language and IDL can be found. -- You are receiving this mail because: You are on the CC list for the bug.
Received on Monday, 12 May 2014 03:55:01 UTC