Summarized test results:
Encoding, double-byte

Intended audience: browser implementers, and anyone who wants to know whether browsers encode and decode according to the Encoding Specification indexes.

These tests check whether browsers encode and decode according to the double-byte algorithms in the Encoding Specification.

To see the test, click on the link in the left-most column. To see detailed results for a single test, click on a row and look just above the table. The detailed results show the date(s) the test result was recorded, and the version of the browser tested.

Any dependencies are shown in notes above the table, and notes below the table will usually provide any additional useful information, including an explanation of why a result was marked as 'partially successful'.

Key:

pass fail partially successful

Results


Legacy multi-byte Chinese (simplified) encodings

GBK

Notes

  1. The following table indicates how many characters were NOT successfully converted. If there is no column for Firefox Nightly, Canary or Webkit, assume that the figures are the same as for the released version.

      Total chars Firefox FNightly Chrome Safari Edge
    gbk-encode-form 23,939 1 1 79 88 80
    gbk-encode-form-errors-misc 3,288 - - 131 181 76
    gbk-encode-form-errors-pua 4,332 - - 81 83 83
    gbk-encode-form-errors-han 7,010 - - 281 451 -
    gbk-encode-form-errors-hangul 11,183 - - - - -
      Total chars Firefox FNightly Chrome Safari Edge
    gbk-encode-href 23,939 1 1 79 88 -
    gbk-encode-href-errors-misc 3,288 - - 131 152 -
    gbk-encode-href-errors-han 7,010 - - 281 451 -
    gbk-encode-href-errors-hangul 11,183 - - - - -
      Total chars Firefox Chrome Canary Safari Edge
    gbk-decode 23,939 1 79 79 80 80
    gbk-decode-errors 5 3 4 4 4 4
  2. Edge fails all href encode tests because characters are not converted to percent-escapes in the href attribute.

  3. Firefox's one failure is this: U+E7C7 %A8%BC assert_equals: expected "%A8%BC" but got "%26%23%35%39%33%33%35%3B". It could be an issue with the test(?).
  4. Additionally, there's a generic problem with handling of ASCII bytes as part of a malformed sequence when decoding. See more info.

GB18030

Notes

  1. The following table indicates how many characters were NOT successfully converted. If there is no column for Firefox Nightly, Canary or Webkit, assume that the figures are the same as for the released version.

      Total chars Firefox Chrome Safari Edge
    gb18030-encode-form-index 23,939 - - 9 1
    gb18030-encode-form-other-misc 3,287 - - 14 -
    gb18030-encode-form-other-pua 4,332 - - - 1
    gb18030-encode-form-other-han 7,010 - - 451 -
    gb18030-encode-form-other-hangul 11,172 - - - -
      Total chars Firefox Chrome Safari Edge
    gb18030-encode-href-index 23,939 - - 9 all
    gb18030-encode-href-other-misc 3,287 - - 14 all
    gb18030-encode-href-other-han 7,010 - - 451 all
    gb18030-encode-href-other-hangul 11,172 - - - all
      Total chars Firefox Chrome Safari Edge
    gb18030-decode-index 23,939 - - - 1
    gb18030-decode-other-misc 3,256 - - - -
    gb18030-decode-other-pua 4,331 - - - -
    gb18030-decode-other-han 7,010 - - - -
    gb18030-decode-other-hangul 11,172 - - - -
    gb18030-decode-errors 5 3 3 3 all
  2. Edge fails all href encode tests because characters are not converted to percent-escapes in the href attribute.

  3. There seems to be a general difference with the spec on the handling of ASCII bytes as part of a malformed sequence. See more info.

Legacy multi-byte Chinese (traditional) encodings

Big5


Notes

  1. The following table indicates how many characters were NOT successfully converted. If there is no column for Firefox Nightly, Canary or Webkit, assume that the figures are the same as for the released version.

      Total chars Firefox Chrome Safari Edge
    big5-encode-form 14,651 - - 1162 1160
    big5-encode-form-errors-misc 3,436 - - 237 89
    big5-encode-form-errors-pua 6,399 - - 6,218 6,218
    big5-encode-form-errors-han 14,409 - - 458 -
    big5-encode-form-errors-extB(1) 21,140 - - - -
    big5-encode-form-errors-extB(2) 21,291 - - - -
    big5-encode-form-errors-hangul 11,183 - - - -
      Total chars Firefox Chrome Safari Edge
    big5-encode-href 14,651 - - 1162 all
    big5-encode-href-errors-misc 3,436 - - 208 all
    big5-encode-href-errors-han 14,409 - - 458 all
    big5-encode-href-errors-hangul 11,183 - - - all
      Total chars Firefox Chrome Safari Edge
    big5-decode 14,651 - - 1,160 1,160
    big5-decode-extra 2,472 - - all all
    big5-decode-errors 8 - - 4 4
  2. Edge fails all href encode tests because characters are not converted to percent-escapes in the href attribute.

  3. These tests have been reviewed and approved.

Legacy multi-byte Japanese encodings

EUC-JP

Notes

  1. The following table indicates how many characters were NOT successfully converted. If there is no column for Firefox Nightly, Canary or Webkit, assume that the figures are the same as for the released version.

      Total chars Firefox FNightly Chrome Safari Edge
    eucjp-encode-form 7,392 - - - 23 2
    eucjp-encode-form-errors-misc 3,431 - - - 344 88
    eucjp-encode-form-errors-han 21,269 - - - 5,971 -
    eucjp-encode-form-errors-hangul 11,183 - - - - -
      Total chars Firefox FNightly Chrome Safari Edge
    eucjp-encode-href 7,392 - - - 23 all
    eucjp-encode-href-errors-misc 3,431 - - - 314 all
    eucjp-encode-href-errors-han 21,269 - - - 5,971 all
    eucjp-encode-href-errors-hangul 11,183 - - - - all
      Total chars Firefox FNightly Chrome Safari Edge
    eucjp-decode 13,495 - - - - 6,067
    eucjp-decode-errors 11 - - - 8 3
  2. Edge fails all href encode tests because characters are not converted to percent-escapes in the href attribute.

  3. eucjp-decode-index: Edge fails on all and only the JIS-X-0212 characters, because it doesn't recognise 0xAF as the first in a 3-byte sequence.

ISO 2022-JP

Notes

  1. The following table indicates how many characters were NOT successfully converted. If there is no column for Firefox Nightly, Canary or Webkit, assume that the figures are the same as for the released version.

      Total chars Firefox FNightly Chrome Safari Edge
    iso2022jp-encode-form 7,329 - - 373 7375 3
    iso2022jp-encode-form-errors-misc 3,462 - - - 3390 150
    iso2022jp-encode-form-errors-han 21,269 - - - 21216 -
    iso2022jp-encode-form-errors-hangul 11,183 - - - 11155 -
      Total chars Firefox FNightly Chrome Safari Edge
    iso2022jp-encode-href 7,329 - - 373 374 all
    iso2022jp-encode-href-errors-misc 3,494 - - - 16 all
    iso2022jp-encode-href-errors-han 21,269 - - - 477 all
    iso2022jp-encode-href-errors-hangul 11,183 - - - - all
      Total chars Firefox FNightly Chrome Safari Edge
    iso2022jp-decode 7,329 - - - - 2
    iso2022jp-decode-errors 8 - - - - all
  2. Edge fails all href encode tests because characters are not converted to percent-escapes in the href attribute.

Shift JIS

Notes

  1. The following table indicates how many characters were NOT successfully converted. If there is no column for Firefox Nightly, Canary or Webkit, assume that the figures are the same as for the released version.

      Total chars Firefox FNightly Chrome Safari Edge
    sjis-encode-form 7,393 - - - 24 2
    sjis-encode-form-errors-misc 3,430 - - - 47 87
    sjis-encode-form-errors-han 21,269 - - - 477 -
    sjis-encode-form-errors-hangul 11,183 - - - - -
      Total chars Firefox FNightly Chrome Safari Edge
    sjis-encode-href 7,393 - - - 24 7,392
    sjis-encode-href-errors-misc 3,430 - - - 17 all
    sjis-encode-href-errors-han 21,269 - - - 477 all
    sjis-encode-href-errors-hangul 11,183 - - - - all
      Total chars Firefox FNightly Chrome Safari Edge
    sjis-decode 7,393 - - - 1 -
    sjis-decode-errors 10 - - - 9 6
  2. Edge fails all href encode tests because characters are not converted to percent-escapes in the href attribute.

  3. These tests have been reviewed and approved.

Legacy multi-byte Korean encodings

EUC-KR

Notes

  1. There are no results for Edge for the href encode tests because characters are not converted to percent-escapes in the href attribute.

  2. The following table indicates how many characters were NOT successfully converted. If there is no column for Firefox Nightly, Canary or Webkit, assume that the figures are the same as for the released version.

      Total chars Firefox Chrome Safari Edge
    euckr-encode-form 17,048 - - 270 8822
    euckr-encode-form-errors-misc 3,119 - - 281 65
    euckr-encode-form-errors-han 23,097 - - 192 -
      Total chars Firefox Chrome Safari Edge
    euckr-encode-href 17,048 - - 270 all
    euckr-encode-href-errors-misc 3,119 - - 254 all
    euckr-encode-href-errors-han 23,097 - - 192 all
      Total chars Firefox Chrome Safari Edge
    euckr-decode 17,048 - - - -
    euckr-decode-errors 8 - - 4 2
  3. Edge fails all href encode tests because characters are not converted to percent-escapes in the href attribute.

  4. euckr-encode-form-index: Edge produces %26%25 for all failed results.

  5. euckr-encode-href-errors: Firefox produces percent-escaped UTF-8 for all failed results. Edge produces named character references

  6. These tests have been reviewed and approved.