The issue involves extending UTF-8 fast paths to handle additional valid encodings.
The issue requires extending the UTF-8 fast paths to accept all valid UTF-8 encodings, including 'UTF8' and 'UTF-8'. The maintainers have discussed whether to use normalizeEncoding or a custom utility, but the final approach is not yet clear. The main blocker is deciding on the implementation method to avoid performance overhead.
UTF8 and UTF-8 are also valid but not accepted by any existing utf8 fast paths (#48658, #49884)
Claim this issue to let others know you're working on it. You'll earn 10 points when you complete it!