Open ArnoldSmith86 opened 1 year ago
OK, the 0
is something we set in widget.js
when catching an exception. So the difference is:
Chrome 109:
Firefox (and Chrome 108):
Apparently somebody added a shortcut for handling empty strings (it does throw an exception if the initial string isn't empty) before checking that the locale is valid.
The fact that ''.toLocaleUpperCase('')
behaves differently makes me pretty confident that this will be fixed in Chromium:
I bisected this to the chromium commit which introduced the change and filed as crbug.com/1409058. Safari does not throw an error for ''.toLocaleLowerCase('')
or ''.toLocaleUpperCase('')
, filed https://bugs.webkit.org/show_bug.cgi?id=250903 for this.
These are the tests that differ:
The last one (
<empty string>
) is the result I get from Chromium 109 on Linux. The one before that (0
) is the result of Firefox 103 on Linux (and has to be what Chromium 108 did). The rest is the command TestCafé uses in theclickRoutine
.