This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
This was was cloned from bug 13800 as part of operation REMIND convergence. Originally filed: 2011-08-17 00:12:00 +0000 Original reporter: Travis Leithead [MSFT] <travil@microsoft.com> ================================================================================ #0 Travis Leithead [MSFT] 2011-08-17 00:12:02 +0000 -------------------------------------------------------------------------------- In order to support suggested changes in CanvasPixelArray -> Uint8ClampedArray (per bug 12586), ArrayBuffer should be specified as a Transferable type in section 2.8.4. Furthermore, in the structured clone algorithm, the cloning of ImageData should be updated to allow the ImageData's Uint8ClampedArray to be transferred: Current text: ↪If input is a ImageData object Let output be a newly constructed ImageData object with the same width and height as input, and with a newly constructed CanvasPixelArray for its data attribute, with the same length and pixel values as the input's. Proposed change: ↪If input is a ImageData object Let output be a newly constructed ImageData object with the same width and height as input, and with a newly constructed Uint8ClampedArray view of the ArrayBuffer in the destination object of memory for its data attribute, with the same length and pixel values as the input's. ...or similar text to indicate that if the ImageData's Uint8ClampedArray's ArrayBuffer is transfered, then the new Uint8ClampedArray instance will be created over the transferred ArrayBuffer. ================================================================================ #1 Ian 'Hixie' Hickson 2011-09-21 22:55:52 +0000 -------------------------------------------------------------------------------- This is being specced in the TypedArray spec for the moment, but it'll come over once it's solid. (kbr: Correct me if I'm wrong here.) ================================================================================ #2 Ian 'Hixie' Hickson 2011-10-19 23:58:35 +0000 -------------------------------------------------------------------------------- Marking this REMIND for now. I will be doing this but we're waiting for the ArrayBuffer part of this to be stable before moving it from ArrayBuffer to HTML. Please don't hesitate to reopen this if you notice that ArrayBuffer is ready for this before I do. ================================================================================ #3 Kenneth Russell 2011-10-20 01:45:49 +0000 -------------------------------------------------------------------------------- I'd like to request review of the changes that were made to the typed array spec today in response to http://www.w3.org/Bugs/Public/show_bug.cgi?id=13799 . Please see https://www.khronos.org/registry/typedarray/specs/latest/ . If they look okay, that's a good indication that they're solidifying. ================================================================================ #4 Ian 'Hixie' Hickson 2011-10-20 05:53:43 +0000 -------------------------------------------------------------------------------- Roger, will do. ================================================================================ #5 Ian 'Hixie' Hickson 2011-10-20 06:19:34 +0000 -------------------------------------------------------------------------------- kbr: The new text looks good. ================================================================================ #6 Ian 'Hixie' Hickson 2011-10-25 04:17:52 +0000 -------------------------------------------------------------------------------- kbr: Do you want me to move this to the HTML spec? Or should I wait? (Either is fine by me.) ================================================================================ #7 Kenneth Russell 2011-10-25 04:59:37 +0000 -------------------------------------------------------------------------------- Thanks for your review above. (In reply to comment #6) > kbr: Do you want me to move this to the HTML spec? Or should I wait? (Either is > fine by me.) Could we hold off a little longer? Ideally I'd like to snapshot the typed array spec again, so that the new functionality isn't highlighted as strawman proposals. If this means closing this bug as REMIND again, no problem; I can take responsibility for reopening it when the next snapshot is taken. ================================================================================ #8 Ian 'Hixie' Hickson 2011-10-25 05:12:12 +0000 -------------------------------------------------------------------------------- Cool, thanks. Will mark it REMIND, just reopen it when you're ready! ================================================================================