W3C home > Mailing lists > Public > public-i18n-core@w3.org > January to March 2015

I18N-ISSUE-440 (BUG27219): Small fixes for TextEncoder.encode() method [encoding]

From: Internationalization Working Group Issue Tracker <sysbot+tracker@w3.org>
Date: Mon, 30 Mar 2015 13:48:51 +0000
To: public-i18n-core@w3.org
Message-Id: <E1Yca3f-000Fmw-MD@deneb.w3.org>
I18N-ISSUE-440 (BUG27219): Small fixes for TextEncoder.encode() method [encoding]

http://www.w3.org/International/track/issues/440

Raised by: Richard Ishida
On product: encoding

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

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

---
Reporter: crimsteam@gmail.com



Hi, I found this small inaccuracy:

https://encoding.spec.whatwg.org/#dom-textencoder-encode

"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
TextEncoder.

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));

</script>

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?
Received on Monday, 30 March 2015 13:48:55 UTC

This archive was generated by hypermail 2.3.1 : Monday, 30 March 2015 13:48:55 UTC