Henri Sivonen

Sorry about the delay. Firefox, Chrome and Safari agree with each other on the 3 remaining failures. Edge is closer to the other browses than to the spec. So I...

Hmm. The Firefox situation might be confused somewhere between the Chrome/Safari behavior and the spec behavior. I need to investigate this more.

OK. Here's what's happening: Firefox implements the spec, but the test case doesn't test the spec. The test case expectations are written as if there was EOF after each examined...

I wrote [demos](https://hsivonen.com/test/moz/gb18030eof/) that exercise both the followed-by-end-tag case and the followed-by-EOF case. The spec, Firefox, Chrome and Safari agree on these, so I think it's the best not to...

Seems minimal-risk, yes. Indeed, the range above the original Big5 range has been mentioned as questionable to include in the encoder before when the range below is excluded.

AFAICT, the gbk tests differ from the spec for one code point to byte pair and vice versa mapping: The tests want `A8` `BC` to decode to U+E7C7 and want...

Additionally, the tests seem to disargee with the spec on the handling of ASCII bytes as part of a malformed sequence when decoding: Fail step 2: 82 30 C3 assert_equals:...

> 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" > > could be an issue with the test(?) That's indeed a test...

There's now an [ICU4X PR](https://github.com/unicode-org/icu4x/pull/1706/) that shows the status of the collator.

Backport in #2153.