ISSUE-440: Small fixes for TextEncoder.encode() method

Small fixes for TextEncoder.encode() method

Raised by:
Richard Ishida
Opened on:

This issue tracks the bug listed above and was created as part of the WG CR process.


Hi, I found this small inaccuracy:

"The encode(input, options) method, when invoked..." << /options/ not exist for
this method, should be just "encode(input)". In algorithm I don't see using
/options/ at least once.

For the same case, in green box, this text can be delete:

"If options's stream is set to true, the method can be invoked multiple times
to process a fragmented stream." << this is funcionality of TextDecoder, not

But in the other site encode() should support streaming like decode()?

I test this in Firefox an Chrome:

<script type = "text/javascript">

alert(new TextEncoder().encode("", 2,2,2,2));


and get the result:

- Chrome works fine, ignores additional arguments
- Firefox throw "TypeError: Argument 2 of TextEncoder.encode can't be converted
to a dictionary". Looks like Firefox take attention to the second argument but
why? Its bug?
Related Actions Items:
No related actions
Related emails:
  1. I18N-ISSUE-440 (BUG27219): Small fixes for TextEncoder.encode() method [encoding] (from on 2015-03-30)

Related notes:

Bug marked RESOLVED and FIXED.

Richard Ishida, 30 Mar 2015, 13:49:20

These issues are now tracked at

Richard Ishida, 16 Sep 2015, 11:55:23

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 $