796327 - Make ArrayBufferView visible

Status: RESOLVED INVALID

(Core :: JavaScript Engine, defect)

Description

[David Teller [:Yoric] - still alive but not very active]

At the moment, there does not seem to be an object ArrayBufferView accessible to JavaScript code. A direct consequence is that there is no good way to check whether a given object is a view.

I may misunderstand the specifications of typed arrays, but I have the impression that ArrayBufferView should be visible.

Comment 1

[Boris Zbarsky [:bzbarsky]]

Spec currently says "[NoInterfaceObject]", so no, there should be no window.ArrayBufferView per spec.

You may also be interested in this thread:

http://www.khronos.org/webgl/public-mailing-list/archives/1206/msg00251.html
http://www.khronos.org/webgl/public-mailing-list/archives/1206/msg00252.html
http://www.khronos.org/webgl/public-mailing-list/archives/1206/msg00253.html
http://www.khronos.org/webgl/public-mailing-list/archives/1206/msg00254.html

which led to the current spec language...

Comment 2

[David Teller [:Yoric] - still alive but not very active]

Ah, I missed that.
Well, I find this a little strange, but if this is in the spec...

Comment 3

[Kenneth Russell]

Per recent discussion on public_webgl, there was agreement that [NoInterfaceObject] should be removed from ArrayBufferView, which has been done. The typed array conformance tests at http://www.khronos.org/registry/webgl/sdk/tests/conformance/typedarrays/array-unit-tests.html have been updated.

Reopening this bug to track exposure of ArrayBufferView in Firefox. Note associated Chromium bug https://code.google.com/p/chromium/issues/detail?id=60449 .

Comment 4

[Nicholas Nethercote [inactive]]

Where is the latest copy of the typed array spec?  I'm looking at http://www.khronos.org/registry/typedarray/specs/latest/#6 and it still says this:

[NoInterfaceObject]
interface ArrayBufferView {
    readonly attribute ArrayBuffer buffer;
    readonly attribute unsigned long byteOffset;
    readonly attribute unsigned long byteLength;
};

Comment 5

[Victor Costan]

According to http://crbug.com/247561 ArrayBufferView is going away. Instead, there will be an ArrayBuffer.isView() that can be used for type checking.

Comment 6

[Nicholas Nethercote [inactive]]

I guess we can close this bug, then?

Comment 7

[Steve Fink [:sfink] [:s:]]

Sounds like we don't need to expose it as a constructor. But it's still unclear to me whether it needs to be on the prototype chain or not.

Comment 8

[Steve Fink [:sfink] [:s:]]

The test at http://www.khronos.org/registry/webgl/sdk/tests/conformance/typedarrays/array-unit-tests.html looks like it doesn't require the extra prototype layer.

Comment 9

[Victor Costan]

Should this morph into "implement ArrayBuffer.isView()", or should I file a different bug for that?

Comment 10

[Nicholas Nethercote [inactive]]

Let's make it a new bug so readers don't have to wade through a bunch of now-irrelevant comments.

Comment 11

[Brandon Benvie [:benvie]]

See bug 896105 for ArrayBuffer.isView.

Comment 12

[Nicholas Nethercote [inactive]]

I guess we didn't actually fix anything...