Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add XMLHttpRequest test with UTF-16-encoded response w/BOM #1586

Closed
hallvors opened this issue Jan 26, 2015 · 2 comments
Closed

Add XMLHttpRequest test with UTF-16-encoded response w/BOM #1586

hallvors opened this issue Jan 26, 2015 · 2 comments
Labels
wg-webapps

Comments

@hallvors
Copy link
Contributor

There's no test that sends back an UTF-16 response with a BOM.
@hallvors hallvors changed the title Add test with UTF-16-encoded response w/BOM Add XMLHttpRequest test with UTF-16-encoded response w/BOM Jan 26, 2015
@hallvors hallvors mentioned this issue Mar 14, 2015
Merged
@hallvors
Copy link
Contributor Author

So, the question - for @annevk and others - is whether a response which is UTF-16 encoded with a UtF-16 BOM should be content-sniffed and decoded as UTF-16 (Chrome does this) or not (Gecko).

@annevk
Copy link
Member

annevk commented Mar 25, 2015

Well the BOM is authoritative. It should not be "sniffed".

@annevk annevk closed this as completed Mar 25, 2015
@ArkadiuszMichalski ArkadiuszMichalski mentioned this issue Apr 26, 2016
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
wg-webapps
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@hallvors @plehegar @annevk