This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
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.
(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