[Bug 26256] New: API: TextEncoder encode()'s 'stream' option appears useless

• From: <bugzilla@jessica.w3.org>
• Date: Wed, 02 Jul 2014 22:21:51 +0000
• To: www-international@w3.org
• Message-ID: <bug-26256-4285@http.www.w3.org/Bugs/Public/>

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

            Bug ID: 26256
           Summary: API: TextEncoder encode()'s 'stream' option appears
                    useless
           Product: WHATWG
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Encoding
          Assignee: annevk@annevk.nl
          Reporter: jsbell@google.com
        QA Contact: sideshowbarker+encodingspec@gmail.com
                CC: mike@w3.org, www-international@w3.org

Given that:

(a) the input to encode() is defined as a ScalarValueString (i.e. no incomplete
surrogate pairs), and 

(b) encode() only supports UTF-8/UTF-16, which do not maintain any encoder
state across input tokens

...then it does not appear that the 'stream' option has any meaningful behavior
for encode().

Am I missing something?

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

Received on Wednesday, 2 July 2014 22:21:52 UTC