ISSUE-375: API: TextEncoder encode()'s 'stream' option appears useless

API: TextEncoder encode()'s 'stream' option appears useless

Raised by:
Addison Phillips
Opened on:

This issue tracks the bug listed above and was created as part of the WG LC process. The bug was created prior to the WG LC.


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?

Related Actions Items:
No related actions
Related emails:
  1. I18N-ISSUE-375 (BUG26256): API: TextEncoder encode()'s 'stream' option appears useless [encoding] (from on 2014-07-10)

Related notes:

This issue was tracked at

Richard Ishida, 16 Sep 2015, 12:20:13

Display change log ATOM feed

Addison Phillips <>, Chair, Richard Ishida <>, Fuqiao Xue <>, Atsushi Shimono <>, Staff Contacts
Tracker: documentation, (configuration for this group), originally developed by Dean Jackson, is developed and maintained by the Systems Team <>.
$Id: index.php,v 1.326 2018/10/13 17:29:51 vivien Exp $