[Bug 26256] API: TextEncoder encode()'s 'stream' option appears useless


Joshua Bell <jsbell@google.com> changed:

           What    |Removed                     |Added
                 CC|                            |hsivonen@hsivonen.fi,
                   |                            |jshin@chromium.org

--- Comment #2 from Joshua Bell <jsbell@google.com> ---
CC: henri, jshin

Unless someone sees how we can write a test for it, we should probably drop it.

(As background: this made sense when we had stateful encodings - i.e. non-UTF
encodings, or when the input was not a ScalarValueString and UTF-16 code units
could be split across DOMStrings.)

You are receiving this mail because:
You are on the CC list for the bug.

Received on Monday, 7 July 2014 16:45:38 UTC