Implement legacy encoders, not just decoders?

[domenic]

jsdom/whatwg-url would use this, to get proper support for the encoding parameter, if it were available! Then anchorElement.search would work correctly in non-UTF-8 documents in jsdom.

[ChALkeR]

@domenic Which error handling mode does that need? html or replacement?

More generically: does anything need a mode that handles encoding errors in any other way than either throw or return a replacement char?

Ref: https://encoding.spec.whatwg.org/#encoders-and-decoders:~:text=to%20output.-,%22html%22,-Push%200x26%20(%26)%2C%200x23

[domenic]

Specifically we need https://url.spec.whatwg.org/#string-percent-encode-after-encoding, which uses https://encoding.spec.whatwg.org/#encode-or-fail, which needs "fatal". (There is no "replacement" for encoders, just for decoders.)

Interestingly, from my reading it looks like throwing is not quite the right behavior; instead it kind of bails out at the first error and returns what it has gotten so far? The note about ISO-2022-JP below #encode-or-fail discusses this a bit.

It's a pretty terrible legacy setup!