XHR fallbacks UTF-8 when invalid encoding is specified

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.

Documentation

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

Specification

Editor's draft

Status in Chromium

Blink components: Blink>Network>XHR

Enabled by default (tracking bug) in:

Chrome for desktop release 74

Consensus & Standardization

After a feature ships in Chrome, the values listed here are not guaranteed to be up to date.

Firefox: Shipped
Edge: No public signals
Safari: In development
Web Developers: No signals

Owner

hiroshige@chromium.org

Last updated on 2019-02-20