> Which MIME type did you use in the response? BOM sniffing in XML is
> non-normative IIRC. For other types, see below.
>
It's text/plain - seems I definitely need one test with an XML response
too.. and one with JSON.
>
> [[
> If charset is null, set charset to utf-8.
>
> Return the result of r
On Mon, 23 Mar 2015 14:32:27 +0100, Hallvord Reiar Michaelsen Steen
wrote:
On Mon, Mar 23, 2015 at 1:45 PM, Simon Pieters wrote:
On Sun, 22 Mar 2015 23:13:20 +0100, Hallvord Reiar Michaelsen Steen <
hst...@mozilla.com> wrote:
Given a server which sends UTF-16 data with a UTF-16 BOM but
On Mon, Mar 23, 2015 at 1:45 PM, Simon Pieters wrote:
> On Sun, 22 Mar 2015 23:13:20 +0100, Hallvord Reiar Michaelsen Steen <
> hst...@mozilla.com> wrote:
>
>
>> Given a server which sends UTF-16 data with a UTF-16 BOM but does *not*
>> send "charset=UTF-16" in the Content-Type header - should th
On Sun, 22 Mar 2015 23:13:20 +0100, Hallvord Reiar Michaelsen Steen
wrote:
Hi,
I've just added a test loading UTF-16 data with XHR, and it exposes an
implementation difference that should probably be discussed:
Given a server which sends UTF-16 data with a UTF-16 BOM but does *not*
send "cha
Hi,
I've just added a test loading UTF-16 data with XHR, and it exposes an
implementation difference that should probably be discussed:
Given a server which sends UTF-16 data with a UTF-16 BOM but does *not*
send "charset=UTF-16" in the Content-Type header - should the browser
detect the encoding,
