Find out which web browsers recognize Byte Order Marks in XMLHttpRequest.responseText with which XMLHttpRequest.overrideMimeType argument.
JavaScript
Switch branches/tags
Nothing to show
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
src
.gitignore
LICENSE
README.markdown
cli.js
kanban.markdown
package.json

README.markdown

test-browser-charsets

Find out which web browsers recognize Byte Order Marks in XMLHttpRequest.responseText with which XMLHttpRequest.overrideMimeType argument.

Overview

  • It is a client-server webapp. Server is implemented using just without any dependencies. Client is plain JavaScript.
  • It is a web developers' tool.
  • It was useful in development of httpinvoke.
  • Helps find out which web browsers recognize Byte Order Marks in XMLHttpRequest.responseText with which XMLHttpRequest.overrideMimeType argument.
  • Shows which byte-order marks were forcibly recognized - files with that BOM byte sequence will have mangled XMLHttpRequest.responseText. Those files are forcibly interpreted as text files, thus you will not be able to download them as binary files. This is irrelevant to Internet Explorer, because it has XMLHttpRequest.responseBody and also the browsers which implement the XMLHttpRequest2.
  • Conclusions:
    • Firefox-based browsers have some charsets that make the BOM ignored: x-user-defined, ibm866, iso-8859-2, etc.
    • WebKit-based browsers always parse the BOM.

Installation

Install with npm:

$ npm install --global test-browser-charsets

CLI

Run:

$ test-browser-charsets

Development

TODO