[encoding] Consider removing TextEncoder support for UTF-16 (#18)

AFAICT, non-UTF-8 encoders are exposed in three places in the Web Platform:

1. TextEncoder
2. Query string parsing for URL and the associated APIs
3. Form submission

URL parsing and form submission use UTF-8 when the encoding of the document is either of the UTF-16 encodings, AFAICT, TextEncoder is the only place where the Web Platform exposes UTF-16 encoder functionality.

This is pretty sad, if TextEncoder support UTF-16 just because it can and the support doesn't have strong use cases.

Am I wrong and do proper use cases exist for UTF-16 in TextEncoder to a degree that sets UTF-16 apart from the other legacy encoding that aren't supported in TextEncoder?

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