André Bargull

> Nonetheless I would suggest that numeric-hour-with-zero-minutes-and-non-zero-seconds.js was clearer using NumberFormat and ListFormat directly, as it previously did, so maybe we should drop the commit ' Use formatDurationFormatPattern for "/numeric-hour-with-zero-minutes-and-non-zero-seconds"'....

Yes, they're valid, but they test a different code path. If we want to keep them, they should be placed into a new file. > How do you suggest we...

Ideas for additional coverage: - Whitespace between and after the padding character `=`, e.g. `Uint8Array.fromBase64("Zg= =")` and `Uint8Array.fromBase64("Zg= = ")`. - `Uint8Array.prototype.setFrom{Base64,Hex}` doesn't modify the typed array when the input...

@tc39/test262-maintainers: "awaiting specification" label can be removed and instead be replaced with "has consensus".

@ptomato The spec polyfill doesn't handle this case correctly.

> There's no ambiguity if it's parsed as @ LeftHandSideExpression MethodDefinition, and it's parsed this way. Here's a simplified version of the current grammar, when you process it with bison...

> [...] do implementations actually execute those implementation-contributed tests? No, because the tests contain implementation internal functions and syntax.

These tests are fixed by #3983.

> Re. M12L, see https://unicode-org.atlassian.net/browse/ICU-22230. It's unfortunate that we have to do this, but as you say, we would need to understand why implementations differ on this point and find...

also mentions that 2033 is a special-case, see section §4.4 "Why is 2033 an exceptional year?". That might explain the ICU4X results.