W3C home > Mailing lists > Public > public-script-coord@w3.org > January to March 2016

[Bug 28798] Indicate BufferSource algorithms can throw

From: <bugzilla@jessica.w3.org>
Date: Wed, 10 Feb 2016 04:09:32 +0000
To: public-script-coord@w3.org
Message-ID: <bug-28798-3890-JXnRnvIts8@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=28798

--- Comment #9 from Tab Atkins Jr. <jackalmage@gmail.com> ---
Ah yeah, I wasn't thinking of the third option - actually stealing ownership of
the buffer.  I wasn't intending that - it's unspecified right now, but FontFace
*should* copy.  IndexedDB, and all the messaging APIs, are doing the same.

Copying is just the safest of all the options.  We *could* design things such
that authors could avoid the copy, by setting some flag or similar on a buffer
that indicates it's a "copy-once" buffer, and loses control of its data when
any API does a copy.  I'm not comfortable doing that by default, tho.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Wednesday, 10 February 2016 04:09:34 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:25 UTC