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

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

State:
CLOSED
Product:
encoding
Raised by:
Addison Phillips
Opened on:
2014-07-10
Description:
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26256

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 sysbot+tracker@w3.org on 2014-07-10)

Related notes:

This issue was tracked at http://www.w3.org/International/docs/encoding/encoding-doc

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

Display change log ATOM feed


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