This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Check if we really need read as Blob (ByteStreamReadType = "blob") functionality on Streams.
Done in ED. Stream will replace most of roles of Blob and most of APIs accept ArrayBuffer. It should be fine not having read as blob functionality.
(In reply to Takeshi Yoshino from comment #1) > Done in ED. Stream will replace most of roles of Blob and most of APIs > accept ArrayBuffer. It should be fine not having read as blob functionality. I meant that use cases where Streams fit more than Blob, once Streams is available we don't need a way to convert data back to Blob. Not meant that Streams completely replace Blob's all use cases. With pipe() and Streams' URL, we can transfer data from source (XHR, etc.) and destination (media elements, etc.) without involving Blob.