This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The expected result <assert-eq>'�'</assert-eq> is wrong - it should be <assert-eq>['�']</assert-eq> <test>parse-json('["\u0000"]', map{'escape':false()})</test> <result> <any-of> <assert-eq>'�'</assert-eq> <error code="FOJS0001"/> </any-of>
Actually I think the result is valid, probably by accident, because ['a'] eq 'a' is true. A better test would be to use deep-equal. But looking at the tests, I don't see any justification in the expected result FOJS0001. I don't think an error result is conformant for either of these two tests.
I've no idea where "FOJS0001" came from either. We were failing the test ['a'] eq 'a' because our test suite harness deliberately tries to avoid using our implementation to test itself and I hadn't updated it to take account of atomization here. I'll switch it to assert-deep-eq and remove the FOJS0001.
Now fixed.