- From: <bugzilla@jessica.w3.org>
- Date: Thu, 11 Feb 2016 15:17:15 +0000
- To: public-script-coord@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28798
Anne <annevk@annevk.nl> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Indicate BufferSource |Make BufferSource more
|algorithms can throw |convenient to use
--- Comment #10 from Anne <annevk@annevk.nl> ---
Here's a strawman:
1. BufferSource (and what it expands to) copies by default. This is safe and
the common case. It gives the specification algorithm to a byte sequence. IDL
handles all exceptional cases.
2. [Detach] BufferSource detaches the buffer source and gives the specification
algorithm access to a byte sequence. This is useful for Web Audio, maybe
elsewhere. IDL handles all exceptional cases.
3. [UnsafeReference] BufferSource gives the specification algorithm to the
JavaScript object. Handle with care. postMessage() and friends will need this.
IDL only performs its normal checks.
--
You are receiving this mail because:
You are on the CC list for the bug.
Received on Thursday, 11 February 2016 15:17:20 UTC