[Bug 24479] New: [Streams] Bug: Unable to notify EOF after delivering the last element separately

https://www.w3.org/Bugs/Public/show_bug.cgi?id=24479

            Bug ID: 24479
           Summary: [Streams] Bug: Unable to notify EOF after delivering
                    the last element separately
           Product: WebAppsWG
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Streams API
          Assignee: tyoshino@google.com
          Reporter: tyoshino@google.com
        QA Contact: public-webapps-bugzilla@w3.org
                CC: mike@w3.org, public-webapps@w3.org

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

-- 
You are receiving this mail because:
You are on the CC list for the bug.

Received on Monday, 3 February 2014 08:36:58 UTC