- From: <bugzilla@jessica.w3.org>
- Date: Tue, 17 Jun 2014 15:31:47 +0000
- To: public-script-coord@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23369 Adrian Bateman [MSFT] <adrianba@microsoft.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |adrianba@microsoft.com --- Comment #16 from Adrian Bateman [MSFT] <adrianba@microsoft.com> --- This topic was discussed for Bug 25966 and Anne suggested that I comment. My proposal is to find a good way to allow the following: 1) Methods should accept either ArrayBuffer or ArrayBufferView. If you have an ArrayBuffer you don't want to have to create a view to be able to use it. Alternatively, you might have a view that maps part of a buffer and you don't want to have to make an ArrayBuffer to use this part. 2) For data being provided in attributes or events, provide it as an ArrayBuffer over which you can create a view if you wish or use it as is. It may be that 8-bit interpretation is the only natural way to read the data but developers can do what they want. >From reading the history here, it looks like the key thing is some simple IDL for accepting the ArrayBuffer or ArrayBufferView (including subclassing, though that's a general issue). -- You are receiving this mail because: You are on the CC list for the bug.
Received on Tuesday, 17 June 2014 15:31:49 UTC