"".localeCompare("\u0000") return -1, should it be 0?

[adamvy]

• Version: v12.16.1
• Platform: Linux 5.5.11 simple/test-crypto-stream broken after openssl upgrade #7 SMP Sat Mar 28 18:31:13 EDT 2020 x86_64 x86_64 x86_64 GNU/Linux

What steps will reproduce the bug?

Evaluate
"".localeCompare("\u0000");

What is the expected behavior?

Firefox reports 0.

ECMA-402 says "The method is required to return +0 when comparing Strings that are considered canonically equivalent by the Unicode standard." https://ecma-international.org/ecma-402/6.0/index.html#sec-collator-comparestrings

What do you see instead?

node reports -1

Additional information

I'm not enough of a Unicode expert to say if "" and "\u0000" are "canonically equivalent" but the inconsistency between firefox and nodejs suggests that one of the two projects has a bug. I reported to firefox here: https://bugzilla.mozilla.org/show_bug.cgi?id=1629547

[addaleax]

@nodejs/i18n-api

[srl295]

The collation weight may matter here, U+0000 NUL is default ignorable, but the left hand side is an empty (0 length) string.

[srl295]

v8 has the same behavior as node.

[devsnek]

┌────────────────┬──────┐
│ ChakraCore     │ 0    │
│ GraalJS        │      │
│ JavaScriptCore │      │
│ SpiderMonkey   │      │
├────────────────┼──────┤
│ QuickJS        │ -1   │
│ V8             │      │
├────────────────┼──────┤
│ Moddable XS    │ -244 │
└────────────────┴──────┘

[srl295]

If this is still an issue it sounds like should be filed against v8

[avivkeller]

$ node                                                           
Welcome to Node.js v22.5.1.
Type ".help" for more information.
> "".localeCompare("\u0000") 
0