XHR fallbacks UTF-8 when invalid encoding is specified

Category: Web Components
Type: New or changed feature
Status: Enabled by default (Chrome 74)
Intent stage: None

Summary

When an invalid encoding is specified for XMLHttpRequest (via overrideMimeType() or the response's mime type), UTF-8 is used e.g. for responseText, which is spec conformant. Previously Latin-1 was used.

Standards & signals

Specification: https://xhr.spec.whatwg.org/#text-response
Firefox: Shipped/Shipping
Safari: In development
Web developers: No signals
Tracking bug: https://bugs.chromium.org/p/chromium/issues/detail?id=905968

Docs: https://github.com/web-platform-tests/wpt/pull/14090

View on chromestatus.com