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 23735 - Failure signaling to object URL created from Stream
Summary: Failure signaling to object URL created from Stream
Status: NEW
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: Streams API (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Takeshi Yoshino
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-06 05:44 UTC by Takeshi Yoshino
Modified: 2013-11-07 19:27 UTC (History)
3 users (show)

See Also:


Attachments

Description Takeshi Yoshino 2013-11-06 05:44:24 UTC
To JS APIs, we can notify any failure of data producer.

However, when data is consumed using URL, it's not trivial. Maybe we should be able to tell the user about the failure, e.g. as an event equivalent to network failure (this is typically observed as a connection terminated without EOF symbol of chunked transfer encoding).
Comment 1 Feras 2013-11-06 07:09:46 UTC
What's the scenario you had in mind for this? I'd imagine the actual consumer of the stream would provide the error information (XHR, Media tag, etc). A good parallel case is the behavior of what happens if you're reading a Blob backed by a file on disk, and the file gets deleted. I'm not sure if we would do something specific for Stream, but I'm interested to hear thoughts on this.
Comment 2 Takeshi Yoshino 2013-11-06 10:26:46 UTC
(In reply to Feras from comment #1)
> What's the scenario you had in mind for this? I'd imagine the actual
> consumer of the stream would provide the error information (XHR, Media tag,
> etc). A good parallel case is the behavior of what happens if you're reading
> a Blob backed by a file on disk, and the file gets deleted.

That's what I imagined.

http://www.w3.org/TR/FileAPI/#dfn-networkError this section has some answer, but not so well-defined.

Since currently abort()-kind functions are omitted from Stream, we cannot explicitly tell the URL to fail loaders. Maybe when garbage collection happens without close() called, do somework to fail load on the object URL?