W3C home > Mailing lists > Public > www-international@w3.org > October to December 2014

[Bug 27219] New: Small fixes for TextEncoder.encode() method.

From: <bugzilla@jessica.w3.org>
Date: Sat, 01 Nov 2014 15:28:19 +0000
To: www-international@w3.org
Message-ID: <bug-27219-4285@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27219

            Bug ID: 27219
           Summary: Small fixes for TextEncoder.encode() method.
           Product: WHATWG
           Version: unspecified
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Encoding
          Assignee: annevk@annevk.nl
          Reporter: crimsteam@gmail.com
        QA Contact: sideshowbarker+encodingspec@gmail.com
                CC: mike@w3.org, www-international@w3.org

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?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Saturday, 1 November 2014 15:28:20 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 21 September 2016 22:37:38 UTC