[whatwg/encoding] "html" error mode somewhat incompatible with URLs (#139)

For some reason I only just realized that the current "`html`" error mode results in URLs where `&` (and `;`) is not escaped. There's quite a few server-side libraries that split on `&` and `;`. Maybe that means we should continue to offer an error mode specifically for URLs that in addition to outputting this sequences, also percent-encodes the `&` and `;` as Chrome appears to be doing.

On the other hand, Firefox has shipped the currently specified behavior and we didn't get bug reports.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/encoding/issues/139