W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > July 2011

[Bug 12586] Suggest using Typed Array for ImageData pixels. Add a new 'buffer' attribute that references ArrayBuffer of the pixel data. Convert 'data' (CanvasPixelArray) to Uint8Array view of 'buffer'.

From: <bugzilla@jessica.w3.org>
Date: Fri, 29 Jul 2011 01:30:22 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1QmbuA-0001gc-MK@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12586

Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ian@hixie.ch,
                   |                            |kbr@google.com

--- Comment #3 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-07-29 01:30:21 UTC ---
It's not quite a typed array. For example, some of the TypedArray constructors
don't make much sense, since the canvas pixel array is based on the underlying
buffer and so the same dimensions can have different buffer sizes.

It might make sense to define some sort of relationship, though.

What's the implementation status of CanvasPixelArray in the various browsers,
in terms of their relationship to TypedArrays? Does anyone else have an
underlying ArrayBuffer like Gecko?

bz: Is the TypedArrayness of CanvasPixelArray in Gecko visible to JS in any
way?

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Friday, 29 July 2011 01:30:23 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:14 UTC