Re: [encoding] iso-2022-jp encoder XSS risks (#15)

I find returning an encoder error (for U+000E and U+000F) with _0xFFFD_ rather than _0x000E_ or _0x000F_ may complicate matters in implementation (this behavior doesn't occur anywhere else in the current Encoding Standard).  For example, my current implementation of character encoders returns a simple error when it is passed an unencodable code point; each character encoder knows about what it's encoding (such as ISO-2022-JP), while code that handles that error (such as a generic error handler that writes HTML escapes) might not.

---
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/encoding/issues/15#issuecomment-174648797