This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 23975 - [Streams API] Remove read as Blob support
Summary: [Streams API] Remove read as Blob support
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: Streams API (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Takeshi Yoshino
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-12-03 15:48 UTC by Takeshi Yoshino
Modified: 2014-02-05 06:29 UTC (History)
2 users (show)

See Also:


Attachments

Description Takeshi Yoshino 2013-12-03 15:48:30 UTC
Check if we really need read as Blob (ByteStreamReadType = "blob") functionality on Streams.
Comment 1 Takeshi Yoshino 2014-01-28 05:29:23 UTC
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.
Comment 2 Takeshi Yoshino 2014-02-05 06:29:50 UTC
(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.