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

Currently https://url.spec.whatwg.org/#query-state does not distinguish between `&` being part of the URL and it coming back from the encode operation.

So we could solve this in the URL Standard instead if we accept that we need to encode code point for code point (to avoid encoding a `&` in the input). (There's probably a more complicated scheme possible here for optimization purposes, but I'm not sure I want the standard to contain that.)

(As far as `<form>` goes, in Chrome this only affects `application/x-www-form-urlencoded` it seems. For `text/plain` and `multipart/form-data` there's no additional percent-encoding. However, it seems that per the URL Standard the appropriate escaping already happens there.)

-- 
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#issuecomment-387656256