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 24479 - [Streams API] Bug: Unable to notify EOF after delivering the last element separately
Summary: [Streams API] Bug: Unable to notify EOF after delivering the last element sep...
Status: RESOLVED WONTFIX
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: Streams API (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Takeshi Yoshino
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-03 08:36 UTC by Takeshi Yoshino
Modified: 2014-10-29 04:06 UTC (History)
2 users (show)

See Also:

Attachments

Description Takeshi Yoshino 2014-02-03 08:36:56 UTC 
After refactoring, the read() API is broken. We cannot notify EOF cleanly without setting fake undefined or null value to result.data if the last data is delivered to the reader without eof set.

Needs fix.

As we haven't received any objection against wait-then-sync-read approach like what I used in the first prototype [1], we can go back to that method again.

[1] http://lists.w3.org/Archives/Public/public-webapps/2013JulSep/0481.html
Comment 1 Takeshi Yoshino 2014-10-29 04:06:48 UTC 
Obsolete