Re: [whatwg/encoding] Encode hook not adequate (#235)

Notes:

1. URL parsing and `application/x-www-form-urlencoded` use shared infrastructure in the specification. `text/plain` does not. Unsure about `multipart/form-data`. (`application/x-www-form-urlencoded` could in theory still use encode/"html" as well because its percent-encode set encompasses `&`, `#`, and `;`, but the way we structure it in the URL Standard seems nicer.)
2. If we want to directly invoke the encoder's handler, the ISO-2022-JP encoder should really do a state transition to ASCII before returning the error. (This is currently handled by the process algorithm putting these ASCII error code points on input so they get encoded, but that would no longer happen.) Presumably no other encoder is affected as they are not stateful?

-- 
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/235#issuecomment-712759102