- From: Henri Sivonen <notifications@github.com>
- Date: Wed, 04 Nov 2015 04:15:33 -0800
- To: whatwg/encoding <encoding@noreply.github.com>
Received on Wednesday, 4 November 2015 12:16:09 UTC
Wow, saying it's `doNotFlush` makes so much more sense than `stream`. Having the spec use "do not flush" as the conceptual flag and then say that for the flag spelled as `stream` is meant to mean "do not flush" would be a huge improvement already. In the Gecko case, a code change is still necessary: The current Gecko behavior doesn't allow you to flush state left around by `stream` by making a subsequent call without `stream`. Another observation: I expect users of the API who think the non-`stream` calls are stateless to be surprised by the BOM-related state surviving a non-`stream` call to `decode()`. --- Reply to this email directly or view it on GitHub: https://github.com/whatwg/encoding/issues/13#issuecomment-153702325
Received on Wednesday, 4 November 2015 12:16:09 UTC