This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 24386 - Consider allowing more encodings in TextEncoder
Summary: Consider allowing more encodings in TextEncoder
Status: RESOLVED WONTFIX
Alias: None
Product: WHATWG
Classification: Unclassified
Component: Encoding (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: Unsorted
Assignee: Anne
QA Contact: sideshowbarker+encodingspec
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-01-24 22:31 UTC by Anne
Modified: 2014-03-27 16:24 UTC (History)
5 users (show)

See Also:

Attachments

Description Anne 2014-01-24 22:31:53 UTC 
People writing web-based email applications have found a need for it.

I'm not entirely opposed I suppose once there's more interoperability among browsers on the encodings.
Comment 1 Henri Sivonen 2014-01-27 12:02:59 UTC 
(In reply to Anne from comment #0)
> People writing web-based email applications have found a need for it.

I think this needs more information about what the need is, etc. So far, it looks like refusing to support non-UTF on the TextEncoder side has been a success by making Gaia email just use UTF-8 (as opposed to e.g. resulting in encoders written in JS):
https://github.com/mozilla-b2g/gaia-email-libs-and-more/blob/master/data/lib/js-shims/faux-encoding.js#L37