This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
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.
How the HTML spec presently defines it: http://www.whatwg.org/specs/web-apps/current-work/multipage/infrastructure.html#dependencies Which declares that ArrayBufferView is simply a type-def of the concrete %TypedArray% classes within ES6.
Note that IDL is global, so since that spec defines it you can use it. Of course for W3C process purposes you may not want a dependency on HTML. :(
https://dvcs.w3.org/hg/webcrypto-api/rev/193c854a9ac7