PSA: XHR now fallbacks to UTF-8 when invalid encoding is specified

28 views
Skip to first unread message

Hiroshige Hayashizaki

unread,
Feb 15, 2019, 6:30:25 PM2/15/19
to blin...@chromium.org, ri...@chromium.org, Yutaka Hirano
Hi Blink-dev,

PSA about the fix of https://crbug.com/905968:
When an invalid encoding is specified for XHR (via overrideMimeType() or response's mime type),
- Previous behavior: Latin-1 was used for decoding (e.g. xhr.responseText).
- New behavior: UTF-8 is used (spec conformant).

Philip Jägenstedt

unread,
Feb 15, 2019, 7:26:58 PM2/15/19
to Hiroshige Hayashizaki, blink-dev, Adam Rice, Yutaka Hirano
Sweet, UTF-8 everywhere!

--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOaYce5EbLhnSv7rYAvOHDnH5XPtUwKpjV3mVSB6YZQJ0heSkg%40mail.gmail.com.

PhistucK

unread,
Feb 16, 2019, 11:14:15 AM2/16/19
to Hiroshige Hayashizaki, blink-dev, Adam Rice, Yutaka Hirano
This might be worth a chromestatus.com entry.

☆PhistucK


--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.

Joe Medley

unread,
Feb 19, 2019, 3:10:37 PM2/19/19
to PhistucK, Hiroshige Hayashizaki, blink-dev, Adam Rice, Yutaka Hirano
I agree.
Joe Medley | Technical Writer, Chrome DevRel | jme...@google.com | 816-678-7195
If an API's not documented it doesn't exist.


To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CABc02_LaZbRDPaEdkpCYMcgqnZPiJmcJ4xqTfXZ6c73oJzO-hQ%40mail.gmail.com.

Hiroshige Hayashizaki

unread,
Feb 19, 2019, 4:24:39 PM2/19/19
to Joe Medley, PhistucK, blink-dev, Adam Rice, Yutaka Hirano
Reply all
Reply to author
Forward
0 new messages