TimeZoneUTCOffsetName and Etc/GMT are ignored in ParseTemporalTimeZoneString

[Constellation]

ParseTemporalTimeZoneString only cares TimeZoneIANAName.
https://tc39.es/proposal-temporal/#sec-temporal-parsetemporaltimezonestring

However, there are other two productions.

TimeZoneBracketedName :
    TimeZoneIANAName
    Etc/GMT ASCIISign Hour
    TimeZoneUTCOffsetName

So, if we use [Etc/GMT-09] etc. then it is ignored in ParseTemporalTimeZoneString.

[justingrant]

This seems like a duplicate (or at least closely related to) the discussion here: #1797 (comment). Want to continue discussion over there?

[ptomato]

Dunno if this is a duplicate - it seems like a related but separate normative change that we should use TimeZoneBracketedName in ParseTemporalTimeZoneString.

[ptomato]

From the other duplicate #1924, this bug causes the assertion in step 5.d of ToTemporalZonedDateTime to fail, as well as the following test262 tests:

• test262/built-ins/Temporal/ZonedDateTime/from/zoneddatetime-sub-minute-offset
• test262/built-ins/Temporal/ZonedDateTime/prototype/equals/sub-minute-offset
• test262/built-ins/Temporal/ZonedDateTime/prototype/since/sub-minute-offset
• test262/built-ins/Temporal/ZonedDateTime/prototype/until/sub-minute-offset

[ptomato]

#1941 is an in-progress attempt to fix this.

[wirthi]

I second that bug.

The newly added built-ins/Temporal/Instant/prototype/toZonedDateTime/timezone-string-multiple-offsets.js and similar also fail because of this.